From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 05:59:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 05:59:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdBgm-0002pw-5S; Wed, 01 Apr 2015 05:59:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdBgl-0002o4-2A for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 05:59:43 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id EE/5D-25404-E498B155; Wed, 01 Apr 2015 05:59:42 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1427867980!13050674!1 X-Originating-IP: [209.85.213.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15956 invoked from network); 1 Apr 2015 05:59:41 -0000 Received: from mail-ig0-f179.google.com (HELO mail-ig0-f179.google.com) (209.85.213.179) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 05:59:41 -0000 Received: by igbud6 with SMTP id ud6so39196118igb.1 for ; Tue, 31 Mar 2015 22:59:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=55gjeK/4IfNjWKOeeY/66hZ2WvIMDhLrJBptVYlfhQI=; b=SKo5s2Y+lG+Boq4IJ3xck6FoJeejaHESW+CfpWkkzaZNGC+eE8uaMqN1Y9vWlO7YFK PTwLa0oiGBEz0DbcEKW1xGWx1DUtQk4x9TIHNnbcGlYCmYxSLuKDGNlXGiT1SA+zbVBJ TU/xmK/Jmjpz4EYxeHGLGYpDzbcvnqE+jtDnVtAHHcQnekqk594bGkviB+8JKWDd2tbm m/Eb0daokJxkBjSy34Ni/ZLCqT17JOBbZf383jk3siDzOeKNJqrd1zcIMKR57EXqvMWf wfwqYta/HrBbEgmvO+7C8229uJ9You3ZWfQPE48rXjMeypb54eAIg5SEKgkXLwN2N9Lg ORuQ== X-Gm-Message-State: ALoCoQkLbYh0wKD3LR6iphouI91tDjMgQqGiYOSPn6inTlApV7azveFVNk1pQLRwmcWCKrp/zm0K MIME-Version: 1.0 X-Received: by 10.42.238.140 with SMTP id ks12mr32483175icb.12.1427867980628; Tue, 31 Mar 2015 22:59:40 -0700 (PDT) Received: by 10.36.54.67 with HTTP; Tue, 31 Mar 2015 22:59:40 -0700 (PDT) In-Reply-To: <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> References: <20150329160245.GA5672@tatooine> <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> Date: Wed, 1 Apr 2015 07:59:40 +0200 Message-ID: From: Magnus Therning To: Anil Madhavapeddy Cc: MirageOS Devel Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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 31 March 2015 at 22:49, Anil Madhavapeddy wrote: > On 31 Mar 2015, at 21:09, David Scott wrote: > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy wrote: >> On 31 Mar 2015, at 07:37, Magnus Therning wrote: >> > After a clean rebuild on my cubieboard, I'm getting the assertion >> > failures too, which is good. I notice the assert that's failing was added >> > relatively recently[1] in tcpip v2.2.3 so it's possible that it's simply >> > highlighting an old bug in mirage-net-xen. The hunt continues... >> >> Ah, that's "good" news indeed. I'll try, but won't make any promises, to >> look a bit at it too. More as a learning exercise then with an aim to >> actually find and fix the issue :) >> >> Excellent bug report Magnus! We didn't catch this due to the lack of >> regular automated testing on ARM. We would catch this on x86 due to >> deploying our sites regularly, but we don't currently run ARM in production. >> I'll rectify this when back in Cambridge with a version of >> www.openmirage.org that runs on a Cubieboard2. >> >> In the meanwhile, would you be able to test if my point release of >> tcpip.2.3.1 fixes your issue? Do >> >> opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 >> >> Once someone with a Cubie2 confirms that the regression has gone, I'll >> push this to OPAM. > > > The mirage-skeleton/static_website works fine for me with that change. > > > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with the > fix. Unfortunately my turn-around time to try out changes varies so I'm happy others react a bit faster :) I'll send a little "me too" when I've had time to verify it too. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus _______________________________________________ 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 Apr 01 05:59:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 05:59:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdBgm-0002pw-5S; Wed, 01 Apr 2015 05:59:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdBgl-0002o4-2A for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 05:59:43 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id EE/5D-25404-E498B155; Wed, 01 Apr 2015 05:59:42 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1427867980!13050674!1 X-Originating-IP: [209.85.213.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15956 invoked from network); 1 Apr 2015 05:59:41 -0000 Received: from mail-ig0-f179.google.com (HELO mail-ig0-f179.google.com) (209.85.213.179) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 05:59:41 -0000 Received: by igbud6 with SMTP id ud6so39196118igb.1 for ; Tue, 31 Mar 2015 22:59:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=55gjeK/4IfNjWKOeeY/66hZ2WvIMDhLrJBptVYlfhQI=; b=SKo5s2Y+lG+Boq4IJ3xck6FoJeejaHESW+CfpWkkzaZNGC+eE8uaMqN1Y9vWlO7YFK PTwLa0oiGBEz0DbcEKW1xGWx1DUtQk4x9TIHNnbcGlYCmYxSLuKDGNlXGiT1SA+zbVBJ TU/xmK/Jmjpz4EYxeHGLGYpDzbcvnqE+jtDnVtAHHcQnekqk594bGkviB+8JKWDd2tbm m/Eb0daokJxkBjSy34Ni/ZLCqT17JOBbZf383jk3siDzOeKNJqrd1zcIMKR57EXqvMWf wfwqYta/HrBbEgmvO+7C8229uJ9You3ZWfQPE48rXjMeypb54eAIg5SEKgkXLwN2N9Lg ORuQ== X-Gm-Message-State: ALoCoQkLbYh0wKD3LR6iphouI91tDjMgQqGiYOSPn6inTlApV7azveFVNk1pQLRwmcWCKrp/zm0K MIME-Version: 1.0 X-Received: by 10.42.238.140 with SMTP id ks12mr32483175icb.12.1427867980628; Tue, 31 Mar 2015 22:59:40 -0700 (PDT) Received: by 10.36.54.67 with HTTP; Tue, 31 Mar 2015 22:59:40 -0700 (PDT) In-Reply-To: <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> References: <20150329160245.GA5672@tatooine> <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> Date: Wed, 1 Apr 2015 07:59:40 +0200 Message-ID: From: Magnus Therning To: Anil Madhavapeddy Cc: MirageOS Devel Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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 31 March 2015 at 22:49, Anil Madhavapeddy wrote: > On 31 Mar 2015, at 21:09, David Scott wrote: > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy wrote: >> On 31 Mar 2015, at 07:37, Magnus Therning wrote: >> > After a clean rebuild on my cubieboard, I'm getting the assertion >> > failures too, which is good. I notice the assert that's failing was added >> > relatively recently[1] in tcpip v2.2.3 so it's possible that it's simply >> > highlighting an old bug in mirage-net-xen. The hunt continues... >> >> Ah, that's "good" news indeed. I'll try, but won't make any promises, to >> look a bit at it too. More as a learning exercise then with an aim to >> actually find and fix the issue :) >> >> Excellent bug report Magnus! We didn't catch this due to the lack of >> regular automated testing on ARM. We would catch this on x86 due to >> deploying our sites regularly, but we don't currently run ARM in production. >> I'll rectify this when back in Cambridge with a version of >> www.openmirage.org that runs on a Cubieboard2. >> >> In the meanwhile, would you be able to test if my point release of >> tcpip.2.3.1 fixes your issue? Do >> >> opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 >> >> Once someone with a Cubie2 confirms that the regression has gone, I'll >> push this to OPAM. > > > The mirage-skeleton/static_website works fine for me with that change. > > > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with the > fix. Unfortunately my turn-around time to try out changes varies so I'm happy others react a bit faster :) I'll send a little "me too" when I've had time to verify it too. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus _______________________________________________ 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 Apr 01 07:15:07 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 07:15:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdCre-0007Ke-Ir; Wed, 01 Apr 2015 07:15:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdCrd-0007Iu-2y for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 07:15:01 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id EA/50-26324-1FA9B155; Wed, 01 Apr 2015 07:14:57 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1427872496!12928916!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12528 invoked from network); 1 Apr 2015 07:14:56 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 07:14:56 -0000 Received: by wgbdm7 with SMTP id dm7so43160146wgb.1 for ; Wed, 01 Apr 2015 00:14:56 -0700 (PDT) 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 :message-id:references:to; bh=GKVMfrXyUBp4x71cZXEGql/5YxflmNNVwzZ39spM1SI=; b=BdTpsMsY9HwiRicyeHuUSc9HHY6kEOzXN9KqB1G4WsqkhMwWNpaW1L/iq+f0uAEIRp EML9hMQ4Wod7FGHKT4eC7GtE7awaAna8lQx6dtjDTjTzgDYZFblKL5xDsszpyhNNFp1C FU/0lWzSJX5gPcMiJjirM1OATK6CIg9ksoRJ5N+4chahfgBkTp4bU5OrNZqiQxE7t8F7 7c16OY3eOYC7V77eh0oPAZAHX/aMmRv6RGzlXzP169+++NwWB5MdW6F6qj3vMitRJB+v p8mYGgWuS02r59rxDz3vdV/9Lug7fYkwqLoqonF6+7zVY6jOAgKhUloNbhW9Vz5Irddi KI3Q== X-Received: by 10.194.83.66 with SMTP id o2mr82072645wjy.55.1427872495972; Wed, 01 Apr 2015 00:14:55 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id i10sm1278841wja.40.2015.04.01.00.14.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 00:14:55 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: <1427844323458.7f2e394e@Nodemailer> Date: Wed, 1 Apr 2015 09:14:53 +0200 Message-Id: <6DB69B82-351C-46F4-AA16-8D3A1A755947@gazagnaire.org> References: <1427844323458.7f2e394e@Nodemailer> To: Joseph Abrahamson X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Interested in Pioneer Projects 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="===============5752198086401846528==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5752198086401846528== Content-Type: multipart/alternative; boundary="Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76" --Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Joseph, > * deflate: I=E2=80=99m interested in streaming algorithms in OCaml = generally. Just an update on this: I've started prototyping = https://github.com/samoht/ocaml-lz77 = and = https://github.com/samoht/ocaml-huffman-code = but there is still work to do: - write the (un)marshalling code for huffman trees - glue everything together using a better streaming API (based on = Daniel's initial design[1]) - benchmarks and comparisons with other implementations (especially [2]) It's not a huge amount of work and they payout is certainly of = high-value: it will help us compile ocaml-git and Irmin to javascript = and run `git push/pull` from a browser (there are other ways to do it, = but that's a cool goal). If you have any questions please ask, Thomas [1] https://gist.github.com/samoht/4e38fb88c8332a044747 = [2] https://code.google.com/p/miniz/ > * WebIDL: I=E2=80=99m very interested in doing front-end work in = js_of_ocaml, though I have no familiarity with WebIDL and am a little = unsure of the purpose here. > * Syslogd: This seems like a simple enough project just to get my feet = wet with unikernel development >=20 > In addition the =E2=80=9Csemantics of mergeable data-structures=E2=80=9D= is interesting, though the description was brief. >=20 > Anyway, I don=E2=80=99t claim to have an enormous amount of free time = and am certainly more interested in just getting my feet wet a bit, but = I=E2=80=99d love to hear from some of the mentors related to each = project and see if anything seems like it might be a reasonable fit for = me. Perhaps the best option would be something with simple and fast = payout that is of high value to the community. I=E2=80=99m more than = happy to do a little grunt work to learn from the best on how to do = OCaml development. >=20 > Cheers, > Joseph Abrahamson >=20 > =E2=80=94 > Sent from Mailbox = _________________________________________= ______ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi Joseph,

* deflate: I=E2=80=99m interested in = streaming algorithms in OCaml = generally.

Just an update on this: I've started = prototyping https://github.com/samoht/ocaml-lz77 and https://github.com/samoht/ocaml-huffman-code
but = there is still work to do:
- write the (un)marshalling code = for huffman trees
- glue everything together using a better = streaming API (based on Daniel's initial design[1])
- = benchmarks and comparisons with other implementations (especially = [2])

It's not a huge amount of work = and they payout is certainly of high-value: it will help us compile = ocaml-git and Irmin to javascript and run `git push/pull` from a browser = (there are other ways to do it, but that's a cool goal).

If you have any questions please = ask,
Thomas

[2] https://code.google.com/p/miniz/



* WebIDL: I=E2=80=99m very interested in doing front-end = work in js_of_ocaml, though I have no familiarity with WebIDL and am a = little unsure of the purpose here.
* Syslogd: This seems like a simple enough project just = to get my feet wet with unikernel development

In addition the =E2=80=9Csemantics of mergeable = data-structures=E2=80=9D is interesting, though the description was = brief.

Anyway, I don=E2=80=99t claim to have an enormous amount = of free time and am certainly more interested in just getting my feet = wet a bit, but I=E2=80=99d love to hear from some of the mentors related = to each project and see if anything seems like it might be a reasonable = fit for me. Perhaps the best option would be something with simple and = fast payout that is of high value to the community. I=E2=80=99m more = than happy to do a little grunt work to learn from the best on how to do = OCaml development.

Cheers,
Joseph Abrahamson

=E2=80=94
Sent from Mailbox
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel

= --Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76-- --===============5752198086401846528== 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 --===============5752198086401846528==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 07:15:07 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 07:15:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdCre-0007Ke-Ir; Wed, 01 Apr 2015 07:15:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdCrd-0007Iu-2y for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 07:15:01 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id EA/50-26324-1FA9B155; Wed, 01 Apr 2015 07:14:57 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1427872496!12928916!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12528 invoked from network); 1 Apr 2015 07:14:56 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 07:14:56 -0000 Received: by wgbdm7 with SMTP id dm7so43160146wgb.1 for ; Wed, 01 Apr 2015 00:14:56 -0700 (PDT) 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 :message-id:references:to; bh=GKVMfrXyUBp4x71cZXEGql/5YxflmNNVwzZ39spM1SI=; b=BdTpsMsY9HwiRicyeHuUSc9HHY6kEOzXN9KqB1G4WsqkhMwWNpaW1L/iq+f0uAEIRp EML9hMQ4Wod7FGHKT4eC7GtE7awaAna8lQx6dtjDTjTzgDYZFblKL5xDsszpyhNNFp1C FU/0lWzSJX5gPcMiJjirM1OATK6CIg9ksoRJ5N+4chahfgBkTp4bU5OrNZqiQxE7t8F7 7c16OY3eOYC7V77eh0oPAZAHX/aMmRv6RGzlXzP169+++NwWB5MdW6F6qj3vMitRJB+v p8mYGgWuS02r59rxDz3vdV/9Lug7fYkwqLoqonF6+7zVY6jOAgKhUloNbhW9Vz5Irddi KI3Q== X-Received: by 10.194.83.66 with SMTP id o2mr82072645wjy.55.1427872495972; Wed, 01 Apr 2015 00:14:55 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id i10sm1278841wja.40.2015.04.01.00.14.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 00:14:55 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: <1427844323458.7f2e394e@Nodemailer> Date: Wed, 1 Apr 2015 09:14:53 +0200 Message-Id: <6DB69B82-351C-46F4-AA16-8D3A1A755947@gazagnaire.org> References: <1427844323458.7f2e394e@Nodemailer> To: Joseph Abrahamson X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Interested in Pioneer Projects 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="===============5752198086401846528==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5752198086401846528== Content-Type: multipart/alternative; boundary="Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76" --Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Joseph, > * deflate: I=E2=80=99m interested in streaming algorithms in OCaml = generally. Just an update on this: I've started prototyping = https://github.com/samoht/ocaml-lz77 = and = https://github.com/samoht/ocaml-huffman-code = but there is still work to do: - write the (un)marshalling code for huffman trees - glue everything together using a better streaming API (based on = Daniel's initial design[1]) - benchmarks and comparisons with other implementations (especially [2]) It's not a huge amount of work and they payout is certainly of = high-value: it will help us compile ocaml-git and Irmin to javascript = and run `git push/pull` from a browser (there are other ways to do it, = but that's a cool goal). If you have any questions please ask, Thomas [1] https://gist.github.com/samoht/4e38fb88c8332a044747 = [2] https://code.google.com/p/miniz/ > * WebIDL: I=E2=80=99m very interested in doing front-end work in = js_of_ocaml, though I have no familiarity with WebIDL and am a little = unsure of the purpose here. > * Syslogd: This seems like a simple enough project just to get my feet = wet with unikernel development >=20 > In addition the =E2=80=9Csemantics of mergeable data-structures=E2=80=9D= is interesting, though the description was brief. >=20 > Anyway, I don=E2=80=99t claim to have an enormous amount of free time = and am certainly more interested in just getting my feet wet a bit, but = I=E2=80=99d love to hear from some of the mentors related to each = project and see if anything seems like it might be a reasonable fit for = me. Perhaps the best option would be something with simple and fast = payout that is of high value to the community. I=E2=80=99m more than = happy to do a little grunt work to learn from the best on how to do = OCaml development. >=20 > Cheers, > Joseph Abrahamson >=20 > =E2=80=94 > Sent from Mailbox = _________________________________________= ______ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi Joseph,

* deflate: I=E2=80=99m interested in = streaming algorithms in OCaml = generally.

Just an update on this: I've started = prototyping https://github.com/samoht/ocaml-lz77 and https://github.com/samoht/ocaml-huffman-code
but = there is still work to do:
- write the (un)marshalling code = for huffman trees
- glue everything together using a better = streaming API (based on Daniel's initial design[1])
- = benchmarks and comparisons with other implementations (especially = [2])

It's not a huge amount of work = and they payout is certainly of high-value: it will help us compile = ocaml-git and Irmin to javascript and run `git push/pull` from a browser = (there are other ways to do it, but that's a cool goal).

If you have any questions please = ask,
Thomas

[2] https://code.google.com/p/miniz/



* WebIDL: I=E2=80=99m very interested in doing front-end = work in js_of_ocaml, though I have no familiarity with WebIDL and am a = little unsure of the purpose here.
* Syslogd: This seems like a simple enough project just = to get my feet wet with unikernel development

In addition the =E2=80=9Csemantics of mergeable = data-structures=E2=80=9D is interesting, though the description was = brief.

Anyway, I don=E2=80=99t claim to have an enormous amount = of free time and am certainly more interested in just getting my feet = wet a bit, but I=E2=80=99d love to hear from some of the mentors related = to each project and see if anything seems like it might be a reasonable = fit for me. Perhaps the best option would be something with simple and = fast payout that is of high value to the community. I=E2=80=99m more = than happy to do a little grunt work to learn from the best on how to do = OCaml development.

Cheers,
Joseph Abrahamson

=E2=80=94
Sent from Mailbox
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel

= --Apple-Mail=_B49DE54F-CFBE-4130-A217-111D849C9B76-- --===============5752198086401846528== 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 --===============5752198086401846528==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 07:53:39 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 07:53: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 1YdDSz-00058I-SU; Wed, 01 Apr 2015 07:53:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdDSy-00058D-1H for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 07:53:36 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id 69/18-09816-FF3AB155; Wed, 01 Apr 2015 07:53:35 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1427874814!14803477!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30814 invoked from network); 1 Apr 2015 07:53:34 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 07:53:34 -0000 Received: by wixo5 with SMTP id o5so23764444wix.1 for ; Wed, 01 Apr 2015 00:53:33 -0700 (PDT) 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 :message-id:references:to; bh=1SUf3xlRZEiROpfVZqVh9RxMSwUKUQeTBNqcXYui/es=; b=JGcauuVg4Z2jiXWvvYtJ7wL0ZNDoDIDRnySLHnh7f8uvtBUnXlBL8Ezq/N35zzepCv C2zQYcuM0IWZ7wnlp3DSGIsUWcW3OTpknWkIg9QaJ1INbzmCxAY0UtOXeJ+Cml/p2Rsi hgPVIlbAtjhUEgbpQb8TIJnw024weZZuG701GlWmXj0AwdF11wjikfUALhQAr/hZ+0KD kH/+p00QKDQ7hm8SRJmTebZPLH8KDUCaeKqYcJi/Drgx0CnM2zpbRIyvxERnVDfz0nY2 80ckrjal7rdIvCdFfKjj6YJD/kmkg5U8H0NgCVZOodQuWpuZLMRRJ0Vju1w8Nzw1SqSh YGtw== X-Received: by 10.194.200.68 with SMTP id jq4mr81957336wjc.58.1427874813807; Wed, 01 Apr 2015 00:53:33 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id m9sm24194760wiz.24.2015.04.01.00.53.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 00:53:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 1 Apr 2015 09:53:31 +0200 Message-Id: <66477998-6372-49E1-B669-8DDCA56E0AA8@gazagnaire.org> References: To: Martin DeMello X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] problem with sqlite constraints and orm 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="===============3759017110842529030==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3759017110842529030== Content-Type: multipart/alternative; boundary="Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6" --Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Martin, I haven't touched at the code of mirage/orm for a very long time (2.5y!) = but I'm not very surprised you can still find bugs in it: the code is = quite fragile (too much camlp4 for its own good) and (mainly) works only = because of the relatively large test-suite. But patches are always very = welcome!=20 Thanks, Thomas > On 30 Mar 2015, at 12:20, Martin DeMello = wrote: >=20 > Problem demonstrated below: violating a unique constraint in sqlite3 = seems to leave things in an inconsistent state. >=20 > Also, tangentially, I discovered this while trying to maintain my own = id on a table because my app is serving json objects over a rest api, = and I need some sort of unique id for clients to be able to send updates = to existing objects. If there were a way to have the autogenerated sql = __id__ column be a record field, that would be extremely useful. >=20 > martin >=20 > $ cat db.ml > type item =3D { > id: int; > } with orm ( > unique: item > ) >=20 > let db_name =3D "test.db" >=20 > $ cat init_db.ml > open Db >=20 > let _ =3D > let db =3D item_init Db.db_name in > let item =3D { > id =3D 1; > } in > item_save db item >=20 >=20 > $ ./init_db.native=20 > $ ./init_db.native=20 > Fatal error: exception Sqlite3.Error("CONSTRAINT") >=20 > $ sqlite3 test.db=20 > sqlite> select * from item; > __id__ id =20 > ---------- ---------- > 1 1 =20 > 2 =20 > sqlite> delete from item; > Error: no such function: SYNC_CACHE_item >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi Martin,

I haven't touched at the code of mirage/orm for a very long = time (2.5y!) but I'm not very surprised you can still find bugs in it: = the code is quite fragile (too much camlp4 for its own good) and = (mainly) works only because of the relatively large test-suite. But = patches are always very welcome! 

Thanks,
Thomas


On 30 Mar 2015, at 12:20, Martin DeMello <martindemello@gmail.com> wrote:

Problem demonstrated below: violating a unique constraint in = sqlite3 seems to leave things in an inconsistent state.

Also, tangentially, I discovered this while = trying to maintain my own id on a table because my app is serving json = objects over a rest api, and I need some sort of unique id for clients = to be able to send updates to existing objects. If there were a way to = have the autogenerated sql __id__ column be a record field, that would = be extremely useful.

martin

$ cat db.ml
type item =3D {
  = id: int;
} with orm (
  unique: = item<id>
)

let db_name = =3D "test.db"

$ cat init_db.ml
open = Db

let _ =3D
  let db =3D = item_init Db.db_name in
  let item =3D {
    id =3D 1;
  } in
  item_save db item


$ ./init_db.native
$ ./init_db.native
Fatal error: exception Sqlite3.Error("CONSTRAINT")

$ sqlite3 test.db
sqlite> = select * from item;
__id__      id   =      
----------  ----------
1           1       =  
2               =      
sqlite> delete from item;
Error: no such function: SYNC_CACHE_item

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

= --Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6-- --===============3759017110842529030== 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 --===============3759017110842529030==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 07:53:39 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 07:53: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 1YdDSz-00058I-SU; Wed, 01 Apr 2015 07:53:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdDSy-00058D-1H for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 07:53:36 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id 69/18-09816-FF3AB155; Wed, 01 Apr 2015 07:53:35 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1427874814!14803477!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30814 invoked from network); 1 Apr 2015 07:53:34 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 07:53:34 -0000 Received: by wixo5 with SMTP id o5so23764444wix.1 for ; Wed, 01 Apr 2015 00:53:33 -0700 (PDT) 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 :message-id:references:to; bh=1SUf3xlRZEiROpfVZqVh9RxMSwUKUQeTBNqcXYui/es=; b=JGcauuVg4Z2jiXWvvYtJ7wL0ZNDoDIDRnySLHnh7f8uvtBUnXlBL8Ezq/N35zzepCv C2zQYcuM0IWZ7wnlp3DSGIsUWcW3OTpknWkIg9QaJ1INbzmCxAY0UtOXeJ+Cml/p2Rsi hgPVIlbAtjhUEgbpQb8TIJnw024weZZuG701GlWmXj0AwdF11wjikfUALhQAr/hZ+0KD kH/+p00QKDQ7hm8SRJmTebZPLH8KDUCaeKqYcJi/Drgx0CnM2zpbRIyvxERnVDfz0nY2 80ckrjal7rdIvCdFfKjj6YJD/kmkg5U8H0NgCVZOodQuWpuZLMRRJ0Vju1w8Nzw1SqSh YGtw== X-Received: by 10.194.200.68 with SMTP id jq4mr81957336wjc.58.1427874813807; Wed, 01 Apr 2015 00:53:33 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id m9sm24194760wiz.24.2015.04.01.00.53.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 00:53:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 1 Apr 2015 09:53:31 +0200 Message-Id: <66477998-6372-49E1-B669-8DDCA56E0AA8@gazagnaire.org> References: To: Martin DeMello X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] problem with sqlite constraints and orm 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="===============3759017110842529030==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3759017110842529030== Content-Type: multipart/alternative; boundary="Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6" --Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Martin, I haven't touched at the code of mirage/orm for a very long time (2.5y!) = but I'm not very surprised you can still find bugs in it: the code is = quite fragile (too much camlp4 for its own good) and (mainly) works only = because of the relatively large test-suite. But patches are always very = welcome!=20 Thanks, Thomas > On 30 Mar 2015, at 12:20, Martin DeMello = wrote: >=20 > Problem demonstrated below: violating a unique constraint in sqlite3 = seems to leave things in an inconsistent state. >=20 > Also, tangentially, I discovered this while trying to maintain my own = id on a table because my app is serving json objects over a rest api, = and I need some sort of unique id for clients to be able to send updates = to existing objects. If there were a way to have the autogenerated sql = __id__ column be a record field, that would be extremely useful. >=20 > martin >=20 > $ cat db.ml > type item =3D { > id: int; > } with orm ( > unique: item > ) >=20 > let db_name =3D "test.db" >=20 > $ cat init_db.ml > open Db >=20 > let _ =3D > let db =3D item_init Db.db_name in > let item =3D { > id =3D 1; > } in > item_save db item >=20 >=20 > $ ./init_db.native=20 > $ ./init_db.native=20 > Fatal error: exception Sqlite3.Error("CONSTRAINT") >=20 > $ sqlite3 test.db=20 > sqlite> select * from item; > __id__ id =20 > ---------- ---------- > 1 1 =20 > 2 =20 > sqlite> delete from item; > Error: no such function: SYNC_CACHE_item >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi Martin,

I haven't touched at the code of mirage/orm for a very long = time (2.5y!) but I'm not very surprised you can still find bugs in it: = the code is quite fragile (too much camlp4 for its own good) and = (mainly) works only because of the relatively large test-suite. But = patches are always very welcome! 

Thanks,
Thomas


On 30 Mar 2015, at 12:20, Martin DeMello <martindemello@gmail.com> wrote:

Problem demonstrated below: violating a unique constraint in = sqlite3 seems to leave things in an inconsistent state.

Also, tangentially, I discovered this while = trying to maintain my own id on a table because my app is serving json = objects over a rest api, and I need some sort of unique id for clients = to be able to send updates to existing objects. If there were a way to = have the autogenerated sql __id__ column be a record field, that would = be extremely useful.

martin

$ cat db.ml
type item =3D {
  = id: int;
} with orm (
  unique: = item<id>
)

let db_name = =3D "test.db"

$ cat init_db.ml
open = Db

let _ =3D
  let db =3D = item_init Db.db_name in
  let item =3D {
    id =3D 1;
  } in
  item_save db item


$ ./init_db.native
$ ./init_db.native
Fatal error: exception Sqlite3.Error("CONSTRAINT")

$ sqlite3 test.db
sqlite> = select * from item;
__id__      id   =      
----------  ----------
1           1       =  
2               =      
sqlite> delete from item;
Error: no such function: SYNC_CACHE_item

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

= --Apple-Mail=_221FC53B-F704-4DB0-A5D4-7AEEAE7321C6-- --===============3759017110842529030== 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 --===============3759017110842529030==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 08:07:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 08:07:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdDga-0007EQ-OL; Wed, 01 Apr 2015 08:07:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdDgZ-0007EL-K0 for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 08:07:39 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id 44/FC-29354-A47AB155; Wed, 01 Apr 2015 08:07:38 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1427875658!13143243!1 X-Originating-IP: [209.85.217.176] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31559 invoked from network); 1 Apr 2015 08:07:38 -0000 Received: from mail-lb0-f176.google.com (HELO mail-lb0-f176.google.com) (209.85.217.176) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 08:07:38 -0000 Received: by lboc7 with SMTP id c7so30272498lbo.1 for ; Wed, 01 Apr 2015 01:07:37 -0700 (PDT) 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:content-transfer-encoding; bh=1eJaEUfIGj8hx3n+nogSODgh8gQiDMOGpWBdFGTgaj8=; b=eWpbK+rqZm0E9ZGGjJmQGlyXr+BKietR8fFIZj7W+BDPrApgyntBx4444nQkjrzcw2 v7Q91h1nE4LQy5fwN+/bGyUnJDfkVzHtOosSv3kcgJqCKgGdJYAL1mY6F/QJjpuVUtTp BY5qnWOVGvsjYBwvGaTXDTIHr0RRB+5sFhsdMDG7MdyooKJ9eAa3pyCO8bSgvAK9pMtf K6keQsDlKzSOLBOnEjZ6IimUQ4DYmcuJwvEaB1sAXlDDs1b3bgqLW5MNIaJh/3D3zP7r ixRLqopsUrWRHOPZ8Nin7bKn0SxXWThZ7xOBhv9xNXReAbybXvg67sBT0tTlZ/q5vhzp Ol4g== MIME-Version: 1.0 X-Received: by 10.112.223.7 with SMTP id qq7mr34597680lbc.81.1427875657654; Wed, 01 Apr 2015 01:07:37 -0700 (PDT) Received: by 10.112.198.38 with HTTP; Wed, 1 Apr 2015 01:07:37 -0700 (PDT) In-Reply-To: <1427844323458.7f2e394e@Nodemailer> References: <1427844323458.7f2e394e@Nodemailer> Date: Wed, 1 Apr 2015 09:07:37 +0100 X-Google-Sender-Auth: f6ytXmLoSdmW2ZSUwxkOksRrfFg Message-ID: From: David Sheets To: Joseph Abrahamson Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Interested in Pioneer Projects 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="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gV2VkLCBBcHIgMSwgMjAxNSBhdCAxMjoyNSBBTSwgSm9zZXBoIEFicmFoYW1zb24KPGpvc2Vw aEByZWlmeWhlYWx0aC5jb20+IHdyb3RlOgo+IEhlbGxvIE1pcmFnZU9TLWRldmVsLAo+Cj4gSeKA mW0gaW50ZXJlc3RlZCBpbiBsZWFybmluZyBtb3JlIGFib3V0IGNvbnRyaWJ1dGluZyB0byBzb21l IHBpb25lZXIgcHJvamVjdHMuCj4gSW4gcGFydGljdWxhciwgdGhlcmUgYXJlIHNldmVyYWwgcHJv amVjdHMgd2hpY2ggSSB3b3VsZG7igJl0IG1pbmQgdGFraW5nIGEKPiBkZWVwZXIgbG9vayBhdDoK Pgo+ICogZGVmbGF0ZTogSeKAmW0gaW50ZXJlc3RlZCBpbiBzdHJlYW1pbmcgYWxnb3JpdGhtcyBp biBPQ2FtbCBnZW5lcmFsbHkuCj4gKiBXZWJJREw6IEnigJltIHZlcnkgaW50ZXJlc3RlZCBpbiBk b2luZyBmcm9udC1lbmQgd29yayBpbiBqc19vZl9vY2FtbCwgdGhvdWdoCj4gSSBoYXZlIG5vIGZh bWlsaWFyaXR5IHdpdGggV2ViSURMIGFuZCBhbSBhIGxpdHRsZSB1bnN1cmUgb2YgdGhlIHB1cnBv c2UKPiBoZXJlLgoKVGhlIHB1cnBvc2Ugb2YgdGhlIFdlYklETCBwcm9qZWN0IGlzIHRvIGJlIGFi bGUgdG8gY29uc3VtZSBicm93c2VyIEFQSQpzcGVjaWZpY2F0aW9ucyBkaXJlY3RseSBmcm9tICJz dGFuZGFyZHMiLgoKT24gdG9wIG9mIHRoaXMsIGpzX29mX29jYW1sIG1hbnVhbCBvciBnZW5lcmF0 ZWQgYmluZGluZ3MgY2FuIGJlCndyaXR0ZW4uIEludGVncmF0aW9uIHdpdGggZ2VuZXJhdG9ycyBs aWtlIGdvamkKPGh0dHBzOi8vZ2l0aHViLmNvbS9rbGFrcGxvay9nb2ppPiBtaWdodCBiZSBhIGdv b2QgaWRlYS4KClRoZSBiYXNpYyB0YXNrIGlzIGp1c3Qgd3JpdGluZyBhIHBhcnNlciBmb3IgV2Vi SURMIGFuZCBkZXNpZ25pbmcgdGhlCmFwcHJvcHJpYXRlIHR5cGVzIHRvIG1hbmlwdWxhdGUgV2Vi SURMIGluIE9DYW1sLiBTZXZlcmFsIGJyb3dzZXJzCmNvbnN1bWUgV2ViSURMIGFuZCBtZXJnZSBp dCB3aXRoIGxvY2FsIGFubm90YXRpb25zIHRvIHByb2R1Y2UgQysrCmludGVyZmFjZXMgdG8gYmUg ZnVsZmlsbGVkIC0tIHdlJ2QgbGlrZSB0byBtZWV0IHRoZW0gYXQgdGhlIHNwZWNpZmllZAppbnRl cmZhY2UgYW5kIGRpcmVjdGx5IGNvbnN1bWUgdGhlaXIgdHlwZWQgc3BlY2lmaWNhdGlvbi4KCklm IHRoZSBwZXJzb24gd2hvIHRha2VzIHRoaXMgcHJvamVjdCBpcyBmYW1pbGlhciB3aXRoIGNvbXBp bGVycywgdHlwZQpkZXNpZ24sIHBhcnNpbmcgYW5kIHNvIG9uLCBpdCBzaG91bGRuJ3QgYmUgaGFy ZCBhdCBhbGwuIFRoZSBkaWZmaWN1bHR5CmluIHRoZSB3b3JrIGRpcmVjdGx5IHJlbGF0ZWQgdG8g dGhlIGFtb3VudCBvZiB3b3JrIGFuZCB0aGUgcGFpbiBvZgp2YWxpZGF0aW5nIGl0IG9uIGEgYnVu Y2ggb2YgV2ViIHNwZWNzLgoKSG9wZSB0aGF0IGhlbHBzLAoKRGF2aWQKCj4gKiBTeXNsb2dkOiBU aGlzIHNlZW1zIGxpa2UgYSBzaW1wbGUgZW5vdWdoIHByb2plY3QganVzdCB0byBnZXQgbXkgZmVl dCB3ZXQKPiB3aXRoIHVuaWtlcm5lbCBkZXZlbG9wbWVudAo+Cj4gSW4gYWRkaXRpb24gdGhlIOKA nHNlbWFudGljcyBvZiBtZXJnZWFibGUgZGF0YS1zdHJ1Y3R1cmVz4oCdIGlzIGludGVyZXN0aW5n LAo+IHRob3VnaCB0aGUgZGVzY3JpcHRpb24gd2FzIGJyaWVmLgo+Cj4gQW55d2F5LCBJIGRvbuKA mXQgY2xhaW0gdG8gaGF2ZSBhbiBlbm9ybW91cyBhbW91bnQgb2YgZnJlZSB0aW1lIGFuZCBhbQo+ IGNlcnRhaW5seSBtb3JlIGludGVyZXN0ZWQgaW4ganVzdCBnZXR0aW5nIG15IGZlZXQgd2V0IGEg Yml0LCBidXQgSeKAmWQgbG92ZSB0bwo+IGhlYXIgZnJvbSBzb21lIG9mIHRoZSBtZW50b3JzIHJl bGF0ZWQgdG8gZWFjaCBwcm9qZWN0IGFuZCBzZWUgaWYgYW55dGhpbmcKPiBzZWVtcyBsaWtlIGl0 IG1pZ2h0IGJlIGEgcmVhc29uYWJsZSBmaXQgZm9yIG1lLiBQZXJoYXBzIHRoZSBiZXN0IG9wdGlv bgo+IHdvdWxkIGJlIHNvbWV0aGluZyB3aXRoIHNpbXBsZSBhbmQgZmFzdCBwYXlvdXQgdGhhdCBp cyBvZiBoaWdoIHZhbHVlIHRvIHRoZQo+IGNvbW11bml0eS4gSeKAmW0gbW9yZSB0aGFuIGhhcHB5 IHRvIGRvIGEgbGl0dGxlIGdydW50IHdvcmsgdG8gbGVhcm4gZnJvbSB0aGUKPiBiZXN0IG9uIGhv dyB0byBkbyBPQ2FtbCBkZXZlbG9wbWVudC4KPgo+IENoZWVycywKPiBKb3NlcGggQWJyYWhhbXNv bgo+Cj4g4oCUCj4gU2VudCBmcm9tIE1haWxib3gKPgo+IF9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fCj4gTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Cj4g TWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKPiBodHRwOi8vbGlzdHMueGVucHJv amVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCj4KCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVs IG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8v bGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRl dmVsCg== From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 08:07:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 08:07:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdDga-0007EQ-OL; Wed, 01 Apr 2015 08:07:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdDgZ-0007EL-K0 for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 08:07:39 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id 44/FC-29354-A47AB155; Wed, 01 Apr 2015 08:07:38 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1427875658!13143243!1 X-Originating-IP: [209.85.217.176] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31559 invoked from network); 1 Apr 2015 08:07:38 -0000 Received: from mail-lb0-f176.google.com (HELO mail-lb0-f176.google.com) (209.85.217.176) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 08:07:38 -0000 Received: by lboc7 with SMTP id c7so30272498lbo.1 for ; Wed, 01 Apr 2015 01:07:37 -0700 (PDT) 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:content-transfer-encoding; bh=1eJaEUfIGj8hx3n+nogSODgh8gQiDMOGpWBdFGTgaj8=; b=eWpbK+rqZm0E9ZGGjJmQGlyXr+BKietR8fFIZj7W+BDPrApgyntBx4444nQkjrzcw2 v7Q91h1nE4LQy5fwN+/bGyUnJDfkVzHtOosSv3kcgJqCKgGdJYAL1mY6F/QJjpuVUtTp BY5qnWOVGvsjYBwvGaTXDTIHr0RRB+5sFhsdMDG7MdyooKJ9eAa3pyCO8bSgvAK9pMtf K6keQsDlKzSOLBOnEjZ6IimUQ4DYmcuJwvEaB1sAXlDDs1b3bgqLW5MNIaJh/3D3zP7r ixRLqopsUrWRHOPZ8Nin7bKn0SxXWThZ7xOBhv9xNXReAbybXvg67sBT0tTlZ/q5vhzp Ol4g== MIME-Version: 1.0 X-Received: by 10.112.223.7 with SMTP id qq7mr34597680lbc.81.1427875657654; Wed, 01 Apr 2015 01:07:37 -0700 (PDT) Received: by 10.112.198.38 with HTTP; Wed, 1 Apr 2015 01:07:37 -0700 (PDT) In-Reply-To: <1427844323458.7f2e394e@Nodemailer> References: <1427844323458.7f2e394e@Nodemailer> Date: Wed, 1 Apr 2015 09:07:37 +0100 X-Google-Sender-Auth: f6ytXmLoSdmW2ZSUwxkOksRrfFg Message-ID: From: David Sheets To: Joseph Abrahamson Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Interested in Pioneer Projects 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="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gV2VkLCBBcHIgMSwgMjAxNSBhdCAxMjoyNSBBTSwgSm9zZXBoIEFicmFoYW1zb24KPGpvc2Vw aEByZWlmeWhlYWx0aC5jb20+IHdyb3RlOgo+IEhlbGxvIE1pcmFnZU9TLWRldmVsLAo+Cj4gSeKA mW0gaW50ZXJlc3RlZCBpbiBsZWFybmluZyBtb3JlIGFib3V0IGNvbnRyaWJ1dGluZyB0byBzb21l IHBpb25lZXIgcHJvamVjdHMuCj4gSW4gcGFydGljdWxhciwgdGhlcmUgYXJlIHNldmVyYWwgcHJv amVjdHMgd2hpY2ggSSB3b3VsZG7igJl0IG1pbmQgdGFraW5nIGEKPiBkZWVwZXIgbG9vayBhdDoK Pgo+ICogZGVmbGF0ZTogSeKAmW0gaW50ZXJlc3RlZCBpbiBzdHJlYW1pbmcgYWxnb3JpdGhtcyBp biBPQ2FtbCBnZW5lcmFsbHkuCj4gKiBXZWJJREw6IEnigJltIHZlcnkgaW50ZXJlc3RlZCBpbiBk b2luZyBmcm9udC1lbmQgd29yayBpbiBqc19vZl9vY2FtbCwgdGhvdWdoCj4gSSBoYXZlIG5vIGZh bWlsaWFyaXR5IHdpdGggV2ViSURMIGFuZCBhbSBhIGxpdHRsZSB1bnN1cmUgb2YgdGhlIHB1cnBv c2UKPiBoZXJlLgoKVGhlIHB1cnBvc2Ugb2YgdGhlIFdlYklETCBwcm9qZWN0IGlzIHRvIGJlIGFi bGUgdG8gY29uc3VtZSBicm93c2VyIEFQSQpzcGVjaWZpY2F0aW9ucyBkaXJlY3RseSBmcm9tICJz dGFuZGFyZHMiLgoKT24gdG9wIG9mIHRoaXMsIGpzX29mX29jYW1sIG1hbnVhbCBvciBnZW5lcmF0 ZWQgYmluZGluZ3MgY2FuIGJlCndyaXR0ZW4uIEludGVncmF0aW9uIHdpdGggZ2VuZXJhdG9ycyBs aWtlIGdvamkKPGh0dHBzOi8vZ2l0aHViLmNvbS9rbGFrcGxvay9nb2ppPiBtaWdodCBiZSBhIGdv b2QgaWRlYS4KClRoZSBiYXNpYyB0YXNrIGlzIGp1c3Qgd3JpdGluZyBhIHBhcnNlciBmb3IgV2Vi SURMIGFuZCBkZXNpZ25pbmcgdGhlCmFwcHJvcHJpYXRlIHR5cGVzIHRvIG1hbmlwdWxhdGUgV2Vi SURMIGluIE9DYW1sLiBTZXZlcmFsIGJyb3dzZXJzCmNvbnN1bWUgV2ViSURMIGFuZCBtZXJnZSBp dCB3aXRoIGxvY2FsIGFubm90YXRpb25zIHRvIHByb2R1Y2UgQysrCmludGVyZmFjZXMgdG8gYmUg ZnVsZmlsbGVkIC0tIHdlJ2QgbGlrZSB0byBtZWV0IHRoZW0gYXQgdGhlIHNwZWNpZmllZAppbnRl cmZhY2UgYW5kIGRpcmVjdGx5IGNvbnN1bWUgdGhlaXIgdHlwZWQgc3BlY2lmaWNhdGlvbi4KCklm IHRoZSBwZXJzb24gd2hvIHRha2VzIHRoaXMgcHJvamVjdCBpcyBmYW1pbGlhciB3aXRoIGNvbXBp bGVycywgdHlwZQpkZXNpZ24sIHBhcnNpbmcgYW5kIHNvIG9uLCBpdCBzaG91bGRuJ3QgYmUgaGFy ZCBhdCBhbGwuIFRoZSBkaWZmaWN1bHR5CmluIHRoZSB3b3JrIGRpcmVjdGx5IHJlbGF0ZWQgdG8g dGhlIGFtb3VudCBvZiB3b3JrIGFuZCB0aGUgcGFpbiBvZgp2YWxpZGF0aW5nIGl0IG9uIGEgYnVu Y2ggb2YgV2ViIHNwZWNzLgoKSG9wZSB0aGF0IGhlbHBzLAoKRGF2aWQKCj4gKiBTeXNsb2dkOiBU aGlzIHNlZW1zIGxpa2UgYSBzaW1wbGUgZW5vdWdoIHByb2plY3QganVzdCB0byBnZXQgbXkgZmVl dCB3ZXQKPiB3aXRoIHVuaWtlcm5lbCBkZXZlbG9wbWVudAo+Cj4gSW4gYWRkaXRpb24gdGhlIOKA nHNlbWFudGljcyBvZiBtZXJnZWFibGUgZGF0YS1zdHJ1Y3R1cmVz4oCdIGlzIGludGVyZXN0aW5n LAo+IHRob3VnaCB0aGUgZGVzY3JpcHRpb24gd2FzIGJyaWVmLgo+Cj4gQW55d2F5LCBJIGRvbuKA mXQgY2xhaW0gdG8gaGF2ZSBhbiBlbm9ybW91cyBhbW91bnQgb2YgZnJlZSB0aW1lIGFuZCBhbQo+ IGNlcnRhaW5seSBtb3JlIGludGVyZXN0ZWQgaW4ganVzdCBnZXR0aW5nIG15IGZlZXQgd2V0IGEg Yml0LCBidXQgSeKAmWQgbG92ZSB0bwo+IGhlYXIgZnJvbSBzb21lIG9mIHRoZSBtZW50b3JzIHJl bGF0ZWQgdG8gZWFjaCBwcm9qZWN0IGFuZCBzZWUgaWYgYW55dGhpbmcKPiBzZWVtcyBsaWtlIGl0 IG1pZ2h0IGJlIGEgcmVhc29uYWJsZSBmaXQgZm9yIG1lLiBQZXJoYXBzIHRoZSBiZXN0IG9wdGlv bgo+IHdvdWxkIGJlIHNvbWV0aGluZyB3aXRoIHNpbXBsZSBhbmQgZmFzdCBwYXlvdXQgdGhhdCBp cyBvZiBoaWdoIHZhbHVlIHRvIHRoZQo+IGNvbW11bml0eS4gSeKAmW0gbW9yZSB0aGFuIGhhcHB5 IHRvIGRvIGEgbGl0dGxlIGdydW50IHdvcmsgdG8gbGVhcm4gZnJvbSB0aGUKPiBiZXN0IG9uIGhv dyB0byBkbyBPQ2FtbCBkZXZlbG9wbWVudC4KPgo+IENoZWVycywKPiBKb3NlcGggQWJyYWhhbXNv bgo+Cj4g4oCUCj4gU2VudCBmcm9tIE1haWxib3gKPgo+IF9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fCj4gTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Cj4g TWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKPiBodHRwOi8vbGlzdHMueGVucHJv amVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCj4KCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVs IG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8v bGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRl dmVsCg== From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 21:15:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 21:15: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 1YdPz2-0004mM-T7; Wed, 01 Apr 2015 21:15:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdPz0-0004mH-MC for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 21:15:30 +0000 Received: from [193.109.254.147] by server-13.bemta-14.messagelabs.com id BB/A0-26939-2FF5C155; Wed, 01 Apr 2015 21:15:30 +0000 X-Env-Sender: joseph@reifyhealth.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1427922927!15012906!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14396 invoked from network); 1 Apr 2015 21:15:28 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 21:15:28 -0000 Received: by qcrf4 with SMTP id f4so40198552qcr.0 for ; Wed, 01 Apr 2015 14:15:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:mime-version:message-id:in-reply-to :references:from:to:cc:subject:content-type; bh=XQvQkYMGJZjJ3uqTUeGRXFkIPCdFbR5N83PSMlH0Gh8=; b=Pz6msZHdTwC7y27FcYJNkO9uOdks9DAFN6nVTa2kfOhSSALen/DdIpbrA59N6otuk7 MaezZrvnm7+zrWVsnShJxedUtH6dvqH7JzAsEcNYPs7t+sQ6rsENhxscutj1+NSQ2lFy INIf+W2HFe0mbY4lpFokGhjRdK2A1QMK4tGD0vKmwkRWSLhnOIgOM+qCi8kY1hUDwN0V CC8rZL+uZz2Mz+8e41qmJ+A6MG2vppPWGGAfbaFBNHcjIoyV62GWbclcAcn9kPJLjsC3 ptRFMr4k+8qq9ErrRsdi8n1QZveepxJidI934yYVysFgoTHFNow2gRTj9n3Ws8eOpC0S 6Z7w== X-Gm-Message-State: ALoCoQmTyUB1ZlXmXCPABeBtUSPVPXkER8VBBZltPK70S9UB3DYrCOwpQ4DzbnbORfehn3Q2B/Lb X-Received: by 10.55.55.4 with SMTP id e4mr92794234qka.97.1427922927367; Wed, 01 Apr 2015 14:15:27 -0700 (PDT) Received: from hedwig-11.prd.orcali.com (ec2-54-85-253-232.compute-1.amazonaws.com. [54.85.253.232]) by mx.google.com with ESMTPSA id j93sm295533qkh.29.2015.04.01.14.15.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 14:15:26 -0700 (PDT) Date: Wed, 01 Apr 2015 14:15:26 -0700 (PDT) X-Google-Original-Date: Wed, 01 Apr 2015 21:15:25 GMT MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1427922925345.4438adcb@Nodemailer> In-Reply-To: References: X-Orchestra-Oid: 84A12B07-765F-4C83-AA23-0AB982B1D9AA X-Orchestra-Sig: 096c4ea0356be9aca5dd9a5084b3031d52cc3af6 X-Orchestra-Thrid: 66DE0901-A93D-4E73-95F1-65D807616B45 X-Orchestra-Thrid-Sig: ffc48b2c0ff3532a07d1d17a4ea760bcaf42acb6 X-Orchestra-Account: e2d34ae8b00765e42966dee2ec4784385b1f3965 From: "Joseph Abrahamson" To: "David Sheets" , "Thomas Gazagnaire" Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Interested in Pioneer Projects 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="===============3924087672472186466==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3924087672472186466== Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1427922926388" ------Nodemailer-0.5.0-?=_1-1427922926388 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thomas, These seem like pretty easy things to bite off. I=E2=80=99ll take a deeper = look and am happy to forward questions to you. David, This seems like a somewhat larger project, but I=E2=80=99m certainly = interested in doing some compiler/type design. I=E2=80=99m still not sure I= yet understand WebIDL, though. The resources I was able to find were quite= dense and I haven=E2=80=99t had the time to sit down and really dig in. I=E2=80=99d be interested in reading some use cases if you have them or any= recommended reading on WebIDL itself. Other example projects would be = valuable to examine as well. =E2=80=94 Sent from Mailbox On Wed, Apr 1, 2015 at 4:07 AM, David Sheets wrote: > On Wed, Apr 1, 2015 at 12:25 AM, Joseph Abrahamson > wrote: >> Hello MirageOS-devel, >> >> I=E2=80=99m interested in learning more about contributing to some = pioneer projects. >> In particular, there are several projects which I wouldn=E2=80=99t mind = taking a >> deeper look at: >> >> * deflate: I=E2=80=99m interested in streaming algorithms in OCaml = generally. >> * WebIDL: I=E2=80=99m very interested in doing front-end work in = js=5Fof=5Focaml, though >> I have no familiarity with WebIDL and am a little unsure of the purpose >> here. > The purpose of the WebIDL project is to be able to consume browser API > specifications directly from =22standards=22. > On top of this, js=5Fof=5Focaml manual or generated bindings can be > written. Integration with generators like goji > might be a good idea. > The basic task is just writing a parser for WebIDL and designing the > appropriate types to manipulate WebIDL in OCaml. Several browsers > consume WebIDL and merge it with local annotations to produce C++ > interfaces to be fulfilled -- we'd like to meet them at the specified > interface and directly consume their typed specification. > If the person who takes this project is familiar with compilers, type > design, parsing and so on, it shouldn't be hard at all. The difficulty > in the work directly related to the amount of work and the pain of > validating it on a bunch of Web specs. > Hope that helps, > David >> * Syslogd: This seems like a simple enough project just to get my feet = wet >> with unikernel development >> >> In addition the =E2=80=9Csemantics of mergeable data-structures=E2=80=9D= is interesting, >> though the description was brief. >> >> Anyway, I don=E2=80=99t claim to have an enormous amount of free time = and am >> certainly more interested in just getting my feet wet a bit, but = I=E2=80=99d love to >> hear from some of the mentors related to each project and see if = anything >> seems like it might be a reasonable fit for me. Perhaps the best option >> would be something with simple and fast payout that is of high value to = the >> community. I=E2=80=99m more than happy to do a little grunt work to = learn from the >> best on how to do OCaml development. >> >> Cheers, >> Joseph Abrahamson >> >> =E2=80=94 >> Sent from Mailbox >> >> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> ------Nodemailer-0.5.0-?=_1-1427922926388 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thomas,

These seem like pretty easy things to bite off. I=E2=80=99ll take a = deeper look and am happy to forward questions to you.

David,

This seems like a somewhat larger project, but I=E2=80=99m certainly = interested in doing some compiler/type design. I=E2=80=99m still not sure I= yet understand WebIDL, though. The resources I was able to find were quite= dense and I haven=E2=80=99t had the time to sit down and really dig in.=

I=E2=80=99d be interested in reading some use cases if you have them = or any recommended reading on WebIDL itself. Other example projects would = be valuable to examine as well.

=E2=80=94
Sent from Mailbox


On Wed, Apr 1, 2015 at 4:07 AM,= David Sheets <sheets@alum.mit.edu> = wrote:

On Wed, Apr 1, = 2015 at 12:25 AM, Joseph Abrahamson
<joseph@reifyhealth.com> wrote:
> Hello MirageOS-devel,
>
> I=E2=80=99m interested in learning more about contributing to some= pioneer projects.
> In particular, there are several projects which I wouldn=E2=80=99t= mind taking a
> deeper look at:
>
> * deflate: I=E2=80=99m interested in streaming algorithms in OCaml= generally.
> * WebIDL: I=E2=80=99m very interested in doing front-end work in = js=5Fof=5Focaml, though
> I have no familiarity with WebIDL and am a little unsure of the = purpose
> here.

The purpose of the WebIDL project is to be able to consume browser = API
specifications directly from =22standards=22.

On top of this, js=5Fof=5Focaml manual or generated bindings can = be
written. Integration with generators like goji
<https://github.com/klakplok/goji> might be a good idea.

The basic task is just writing a parser for WebIDL and designing = the
appropriate types to manipulate WebIDL in OCaml. Several browsers
consume WebIDL and merge it with local annotations to produce C++
interfaces to be fulfilled -- we'd like to meet them at the specified
interface and directly consume their typed specification.

If the person who takes this project is familiar with compilers, = type
design, parsing and so on, it shouldn't be hard at all. The difficulty
in the work directly related to the amount of work and the pain of
validating it on a bunch of Web specs.

Hope that helps,

David

> * Syslogd: This seems like a simple enough project just to get= my feet wet
> with unikernel development
>
> In addition the =E2=80=9Csemantics of mergeable = data-structures=E2=80=9D is interesting,
> though the description was brief.
>
> Anyway, I don=E2=80=99t claim to have an enormous amount of free = time and am
> certainly more interested in just getting my feet wet a bit, but = I=E2=80=99d love to
> hear from some of the mentors related to each project and see if = anything
> seems like it might be a reasonable fit for me. Perhaps the best = option
> would be something with simple and fast payout that is of high = value to the
> community. I=E2=80=99m more than happy to do a little grunt work = to learn from the
> best on how to do OCaml development.
>
> Cheers,
> Joseph Abrahamson
>
> =E2=80=94
> Sent from Mailbox
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-deve= l
>


------Nodemailer-0.5.0-?=_1-1427922926388-- --===============3924087672472186466== 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 --===============3924087672472186466==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 21:15:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 21:15: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 1YdPz2-0004mM-T7; Wed, 01 Apr 2015 21:15:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdPz0-0004mH-MC for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 21:15:30 +0000 Received: from [193.109.254.147] by server-13.bemta-14.messagelabs.com id BB/A0-26939-2FF5C155; Wed, 01 Apr 2015 21:15:30 +0000 X-Env-Sender: joseph@reifyhealth.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1427922927!15012906!1 X-Originating-IP: [209.85.216.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14396 invoked from network); 1 Apr 2015 21:15:28 -0000 Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 21:15:28 -0000 Received: by qcrf4 with SMTP id f4so40198552qcr.0 for ; Wed, 01 Apr 2015 14:15:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:mime-version:message-id:in-reply-to :references:from:to:cc:subject:content-type; bh=XQvQkYMGJZjJ3uqTUeGRXFkIPCdFbR5N83PSMlH0Gh8=; b=Pz6msZHdTwC7y27FcYJNkO9uOdks9DAFN6nVTa2kfOhSSALen/DdIpbrA59N6otuk7 MaezZrvnm7+zrWVsnShJxedUtH6dvqH7JzAsEcNYPs7t+sQ6rsENhxscutj1+NSQ2lFy INIf+W2HFe0mbY4lpFokGhjRdK2A1QMK4tGD0vKmwkRWSLhnOIgOM+qCi8kY1hUDwN0V CC8rZL+uZz2Mz+8e41qmJ+A6MG2vppPWGGAfbaFBNHcjIoyV62GWbclcAcn9kPJLjsC3 ptRFMr4k+8qq9ErrRsdi8n1QZveepxJidI934yYVysFgoTHFNow2gRTj9n3Ws8eOpC0S 6Z7w== X-Gm-Message-State: ALoCoQmTyUB1ZlXmXCPABeBtUSPVPXkER8VBBZltPK70S9UB3DYrCOwpQ4DzbnbORfehn3Q2B/Lb X-Received: by 10.55.55.4 with SMTP id e4mr92794234qka.97.1427922927367; Wed, 01 Apr 2015 14:15:27 -0700 (PDT) Received: from hedwig-11.prd.orcali.com (ec2-54-85-253-232.compute-1.amazonaws.com. [54.85.253.232]) by mx.google.com with ESMTPSA id j93sm295533qkh.29.2015.04.01.14.15.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 14:15:26 -0700 (PDT) Date: Wed, 01 Apr 2015 14:15:26 -0700 (PDT) X-Google-Original-Date: Wed, 01 Apr 2015 21:15:25 GMT MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1427922925345.4438adcb@Nodemailer> In-Reply-To: References: X-Orchestra-Oid: 84A12B07-765F-4C83-AA23-0AB982B1D9AA X-Orchestra-Sig: 096c4ea0356be9aca5dd9a5084b3031d52cc3af6 X-Orchestra-Thrid: 66DE0901-A93D-4E73-95F1-65D807616B45 X-Orchestra-Thrid-Sig: ffc48b2c0ff3532a07d1d17a4ea760bcaf42acb6 X-Orchestra-Account: e2d34ae8b00765e42966dee2ec4784385b1f3965 From: "Joseph Abrahamson" To: "David Sheets" , "Thomas Gazagnaire" Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Interested in Pioneer Projects 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="===============3924087672472186466==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3924087672472186466== Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1427922926388" ------Nodemailer-0.5.0-?=_1-1427922926388 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thomas, These seem like pretty easy things to bite off. I=E2=80=99ll take a deeper = look and am happy to forward questions to you. David, This seems like a somewhat larger project, but I=E2=80=99m certainly = interested in doing some compiler/type design. I=E2=80=99m still not sure I= yet understand WebIDL, though. The resources I was able to find were quite= dense and I haven=E2=80=99t had the time to sit down and really dig in. I=E2=80=99d be interested in reading some use cases if you have them or any= recommended reading on WebIDL itself. Other example projects would be = valuable to examine as well. =E2=80=94 Sent from Mailbox On Wed, Apr 1, 2015 at 4:07 AM, David Sheets wrote: > On Wed, Apr 1, 2015 at 12:25 AM, Joseph Abrahamson > wrote: >> Hello MirageOS-devel, >> >> I=E2=80=99m interested in learning more about contributing to some = pioneer projects. >> In particular, there are several projects which I wouldn=E2=80=99t mind = taking a >> deeper look at: >> >> * deflate: I=E2=80=99m interested in streaming algorithms in OCaml = generally. >> * WebIDL: I=E2=80=99m very interested in doing front-end work in = js=5Fof=5Focaml, though >> I have no familiarity with WebIDL and am a little unsure of the purpose >> here. > The purpose of the WebIDL project is to be able to consume browser API > specifications directly from =22standards=22. > On top of this, js=5Fof=5Focaml manual or generated bindings can be > written. Integration with generators like goji > might be a good idea. > The basic task is just writing a parser for WebIDL and designing the > appropriate types to manipulate WebIDL in OCaml. Several browsers > consume WebIDL and merge it with local annotations to produce C++ > interfaces to be fulfilled -- we'd like to meet them at the specified > interface and directly consume their typed specification. > If the person who takes this project is familiar with compilers, type > design, parsing and so on, it shouldn't be hard at all. The difficulty > in the work directly related to the amount of work and the pain of > validating it on a bunch of Web specs. > Hope that helps, > David >> * Syslogd: This seems like a simple enough project just to get my feet = wet >> with unikernel development >> >> In addition the =E2=80=9Csemantics of mergeable data-structures=E2=80=9D= is interesting, >> though the description was brief. >> >> Anyway, I don=E2=80=99t claim to have an enormous amount of free time = and am >> certainly more interested in just getting my feet wet a bit, but = I=E2=80=99d love to >> hear from some of the mentors related to each project and see if = anything >> seems like it might be a reasonable fit for me. Perhaps the best option >> would be something with simple and fast payout that is of high value to = the >> community. I=E2=80=99m more than happy to do a little grunt work to = learn from the >> best on how to do OCaml development. >> >> Cheers, >> Joseph Abrahamson >> >> =E2=80=94 >> Sent from Mailbox >> >> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> ------Nodemailer-0.5.0-?=_1-1427922926388 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thomas,

These seem like pretty easy things to bite off. I=E2=80=99ll take a = deeper look and am happy to forward questions to you.

David,

This seems like a somewhat larger project, but I=E2=80=99m certainly = interested in doing some compiler/type design. I=E2=80=99m still not sure I= yet understand WebIDL, though. The resources I was able to find were quite= dense and I haven=E2=80=99t had the time to sit down and really dig in.=

I=E2=80=99d be interested in reading some use cases if you have them = or any recommended reading on WebIDL itself. Other example projects would = be valuable to examine as well.

=E2=80=94
Sent from Mailbox


On Wed, Apr 1, 2015 at 4:07 AM,= David Sheets <sheets@alum.mit.edu> = wrote:

On Wed, Apr 1, = 2015 at 12:25 AM, Joseph Abrahamson
<joseph@reifyhealth.com> wrote:
> Hello MirageOS-devel,
>
> I=E2=80=99m interested in learning more about contributing to some= pioneer projects.
> In particular, there are several projects which I wouldn=E2=80=99t= mind taking a
> deeper look at:
>
> * deflate: I=E2=80=99m interested in streaming algorithms in OCaml= generally.
> * WebIDL: I=E2=80=99m very interested in doing front-end work in = js=5Fof=5Focaml, though
> I have no familiarity with WebIDL and am a little unsure of the = purpose
> here.

The purpose of the WebIDL project is to be able to consume browser = API
specifications directly from =22standards=22.

On top of this, js=5Fof=5Focaml manual or generated bindings can = be
written. Integration with generators like goji
<https://github.com/klakplok/goji> might be a good idea.

The basic task is just writing a parser for WebIDL and designing = the
appropriate types to manipulate WebIDL in OCaml. Several browsers
consume WebIDL and merge it with local annotations to produce C++
interfaces to be fulfilled -- we'd like to meet them at the specified
interface and directly consume their typed specification.

If the person who takes this project is familiar with compilers, = type
design, parsing and so on, it shouldn't be hard at all. The difficulty
in the work directly related to the amount of work and the pain of
validating it on a bunch of Web specs.

Hope that helps,

David

> * Syslogd: This seems like a simple enough project just to get= my feet wet
> with unikernel development
>
> In addition the =E2=80=9Csemantics of mergeable = data-structures=E2=80=9D is interesting,
> though the description was brief.
>
> Anyway, I don=E2=80=99t claim to have an enormous amount of free = time and am
> certainly more interested in just getting my feet wet a bit, but = I=E2=80=99d love to
> hear from some of the mentors related to each project and see if = anything
> seems like it might be a reasonable fit for me. Perhaps the best = option
> would be something with simple and fast payout that is of high = value to the
> community. I=E2=80=99m more than happy to do a little grunt work = to learn from the
> best on how to do OCaml development.
>
> Cheers,
> Joseph Abrahamson
>
> =E2=80=94
> Sent from Mailbox
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-deve= l
>


------Nodemailer-0.5.0-?=_1-1427922926388-- --===============3924087672472186466== 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 --===============3924087672472186466==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 01 21:22:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 21:22: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 1YdQ5k-0005Y8-F0; Wed, 01 Apr 2015 21:22:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdQ5k-0005Y3-2B for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 21:22:28 +0000 Received: from [193.109.254.147] by server-11.bemta-14.messagelabs.com id 91/3D-22533-3916C155; Wed, 01 Apr 2015 21:22:27 +0000 X-Env-Sender: martindemello@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1427923345!15027109!1 X-Originating-IP: [209.85.216.174] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28402 invoked from network); 1 Apr 2015 21:22:26 -0000 Received: from mail-qc0-f174.google.com (HELO mail-qc0-f174.google.com) (209.85.216.174) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 21:22:26 -0000 Received: by qcay5 with SMTP id y5so52706607qca.1 for ; Wed, 01 Apr 2015 14:22:25 -0700 (PDT) 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=HgpFXJmJXt/zU61nZz9Hd3hO6f94msCmknZy7tRD8Bg=; b=j9UkHJRqt+r2rrdn7P8iJk5BaFZ5j9YUxlKkz3mf665UKDmtuEh8IvH84SQ6lB04zV 14cEBrmilHtvzDttqgGQnBA6tNFijRGu2K7xAVcsnHyVPAKMQIBZImVjPT9d0s9L7gWP 3cSupKT2XMP2tUHbUs+zVoljCXjoDlp16pKGt1reaeHtLTQzgUlyNFg1f/C/Qjw+cxj6 Jbj9A5x86gupFvP0rUTo0OwVux4Bz9gZIzkR26KLewhuo+o7KjWoe8hjmMnhhDnJIQDQ D0vnhHMV4rXXHcyj8X6iSk87n8wakdazBHjTryrhIGyN2c/akauoBDlIbSqso69eaH7P FMDg== MIME-Version: 1.0 X-Received: by 10.140.232.15 with SMTP id d15mr59412098qhc.52.1427923345363; Wed, 01 Apr 2015 14:22:25 -0700 (PDT) Received: by 10.140.47.55 with HTTP; Wed, 1 Apr 2015 14:22:25 -0700 (PDT) In-Reply-To: <66477998-6372-49E1-B669-8DDCA56E0AA8@gazagnaire.org> References: <66477998-6372-49E1-B669-8DDCA56E0AA8@gazagnaire.org> Date: Wed, 1 Apr 2015 14:22:25 -0700 Message-ID: From: Martin DeMello To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] problem with sqlite constraints and orm 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 there a more current option people are using for working with a database? I'd be happy to poke at the orm code in the longer term, but I also want to get on with writing my actual app :) martin On Wed, Apr 1, 2015 at 12:53 AM, Thomas Gazagnaire wrote: > Hi Martin, > > I haven't touched at the code of mirage/orm for a very long time (2.5y!) but > I'm not very surprised you can still find bugs in it: the code is quite > fragile (too much camlp4 for its own good) and (mainly) works only because > of the relatively large test-suite. But patches are always very welcome! > > Thanks, > Thomas > > > On 30 Mar 2015, at 12:20, Martin DeMello wrote: > > Problem demonstrated below: violating a unique constraint in sqlite3 seems > to leave things in an inconsistent state. > > Also, tangentially, I discovered this while trying to maintain my own id on > a table because my app is serving json objects over a rest api, and I need > some sort of unique id for clients to be able to send updates to existing > objects. If there were a way to have the autogenerated sql __id__ column be > a record field, that would be extremely useful. > > martin > > $ cat db.ml > type item = { > id: int; > } with orm ( > unique: item > ) > > let db_name = "test.db" > > $ cat init_db.ml > open Db > > let _ = > let db = item_init Db.db_name in > let item = { > id = 1; > } in > item_save db item > > > $ ./init_db.native > $ ./init_db.native > Fatal error: exception Sqlite3.Error("CONSTRAINT") > > $ sqlite3 test.db > sqlite> select * from item; > __id__ id > ---------- ---------- > 1 1 > 2 > sqlite> delete from item; > Error: no such function: SYNC_CACHE_item > > _______________________________________________ > 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 Apr 01 21:22:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Apr 2015 21:22: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 1YdQ5k-0005Y8-F0; Wed, 01 Apr 2015 21:22:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdQ5k-0005Y3-2B for mirageos-devel@lists.xenproject.org; Wed, 01 Apr 2015 21:22:28 +0000 Received: from [193.109.254.147] by server-11.bemta-14.messagelabs.com id 91/3D-22533-3916C155; Wed, 01 Apr 2015 21:22:27 +0000 X-Env-Sender: martindemello@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1427923345!15027109!1 X-Originating-IP: [209.85.216.174] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28402 invoked from network); 1 Apr 2015 21:22:26 -0000 Received: from mail-qc0-f174.google.com (HELO mail-qc0-f174.google.com) (209.85.216.174) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2015 21:22:26 -0000 Received: by qcay5 with SMTP id y5so52706607qca.1 for ; Wed, 01 Apr 2015 14:22:25 -0700 (PDT) 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=HgpFXJmJXt/zU61nZz9Hd3hO6f94msCmknZy7tRD8Bg=; b=j9UkHJRqt+r2rrdn7P8iJk5BaFZ5j9YUxlKkz3mf665UKDmtuEh8IvH84SQ6lB04zV 14cEBrmilHtvzDttqgGQnBA6tNFijRGu2K7xAVcsnHyVPAKMQIBZImVjPT9d0s9L7gWP 3cSupKT2XMP2tUHbUs+zVoljCXjoDlp16pKGt1reaeHtLTQzgUlyNFg1f/C/Qjw+cxj6 Jbj9A5x86gupFvP0rUTo0OwVux4Bz9gZIzkR26KLewhuo+o7KjWoe8hjmMnhhDnJIQDQ D0vnhHMV4rXXHcyj8X6iSk87n8wakdazBHjTryrhIGyN2c/akauoBDlIbSqso69eaH7P FMDg== MIME-Version: 1.0 X-Received: by 10.140.232.15 with SMTP id d15mr59412098qhc.52.1427923345363; Wed, 01 Apr 2015 14:22:25 -0700 (PDT) Received: by 10.140.47.55 with HTTP; Wed, 1 Apr 2015 14:22:25 -0700 (PDT) In-Reply-To: <66477998-6372-49E1-B669-8DDCA56E0AA8@gazagnaire.org> References: <66477998-6372-49E1-B669-8DDCA56E0AA8@gazagnaire.org> Date: Wed, 1 Apr 2015 14:22:25 -0700 Message-ID: From: Martin DeMello To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] problem with sqlite constraints and orm 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 there a more current option people are using for working with a database? I'd be happy to poke at the orm code in the longer term, but I also want to get on with writing my actual app :) martin On Wed, Apr 1, 2015 at 12:53 AM, Thomas Gazagnaire wrote: > Hi Martin, > > I haven't touched at the code of mirage/orm for a very long time (2.5y!) but > I'm not very surprised you can still find bugs in it: the code is quite > fragile (too much camlp4 for its own good) and (mainly) works only because > of the relatively large test-suite. But patches are always very welcome! > > Thanks, > Thomas > > > On 30 Mar 2015, at 12:20, Martin DeMello wrote: > > Problem demonstrated below: violating a unique constraint in sqlite3 seems > to leave things in an inconsistent state. > > Also, tangentially, I discovered this while trying to maintain my own id on > a table because my app is serving json objects over a rest api, and I need > some sort of unique id for clients to be able to send updates to existing > objects. If there were a way to have the autogenerated sql __id__ column be > a record field, that would be extremely useful. > > martin > > $ cat db.ml > type item = { > id: int; > } with orm ( > unique: item > ) > > let db_name = "test.db" > > $ cat init_db.ml > open Db > > let _ = > let db = item_init Db.db_name in > let item = { > id = 1; > } in > item_save db item > > > $ ./init_db.native > $ ./init_db.native > Fatal error: exception Sqlite3.Error("CONSTRAINT") > > $ sqlite3 test.db > sqlite> select * from item; > __id__ id > ---------- ---------- > 1 1 > 2 > sqlite> delete from item; > Error: no such function: SYNC_CACHE_item > > _______________________________________________ > 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 Thu Apr 02 20:19:07 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Apr 2015 20:19:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdlZq-0006rE-Pi; Thu, 02 Apr 2015 20:18:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdlZq-0006qm-A5 for mirageos-devel@lists.xenproject.org; Thu, 02 Apr 2015 20:18:58 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 34/5C-23555-134AD155; Thu, 02 Apr 2015 20:18:57 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-4.tower-31.messagelabs.com!1428005936!13477268!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31546 invoked from network); 2 Apr 2015 20:18:56 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2015 20:18:56 -0000 Received: by lagg8 with SMTP id g8so68165501lag.1 for ; Thu, 02 Apr 2015 13:18:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=CkL91RZWQqpBmUtLnmYRI8xWXQmWsf7UQPhhvqTvALw=; b=T+EP8n1ehEJ/SnTNFuwamDflqURSbFT4L9OH2B4CE/ye5lKMaUQEWuFSA8PZqyMVUr ziWzawBMAGhLb0XkdYlQICjeaH4IbUNeRvxX+l0IlLfbJ6dCJ6bfhXI1cttE7QRk8Wfw dCPqm9RPw45j0z6x8yAxrq0kYVkb4hUa3kGEsmZVfeUpu31lT3seGD3X98bft1eOhvMV RBcHM0QUdaz4zWiAMdHrAz1GS8V1KOu2xTlLPuajnosPhu9vGJWn5zasTHfMcHb1L3bC iM/jdr35dFw5kTmKXPhv46ecUePcSfkooXwWrVoZqAivRNjke8tr0jr/nJC1uS+Mo+RX HBlw== X-Gm-Message-State: ALoCoQkKXMLzJQUM2Ykizl4mnc5ZmAcw57MvYk6MgM4k+FIFbb3wljijo4cCHE+Vzp7JAj2Dq4Up X-Received: by 10.112.136.232 with SMTP id qd8mr23706322lbb.1.1428005935849; Thu, 02 Apr 2015 13:18:55 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id t3sm1197519lag.15.2015.04.02.13.18.53 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2015 13:18:54 -0700 (PDT) Date: Thu, 2 Apr 2015 22:18:51 +0200 From: Magnus Therning To: mirageos-devel@lists.xenproject.org Message-ID: <20150402201851.GA10627@tatooine> References: <20150329160245.GA5672@tatooine> <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> MIME-Version: 1.0 In-Reply-To: <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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="===============4090709698408854979==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4090709698408854979== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote: > On 31 Mar 2015, at 21:09, David Scott wrote: > >=20 > >=20 > >=20 > > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy > wrote: > > On 31 Mar 2015, at 07:37, Magnus Therning > wrote: > >>=20 > >> > After a clean rebuild on my cubieboard, I'm getting the assertion fa= ilures too, which is good. I notice the assert that's failing was added rel= atively recently[1] in tcpip v2.2.3 so it's possible that it's simply highl= ighting an old bug in mirage-net-xen. The hunt continues... >>>=20 >>> Ah, that's "good" news indeed. I'll try, but won't make any promises, t= o look a bit at it too. More as a learning exercise then with an aim to act= ually find and fix the issue :) >>>=20 >> Excellent bug report Magnus! We didn't catch this due to the lack of re= gular automated testing on ARM. We would catch this on x86 due to deployin= g our sites regularly, but we don't currently run ARM in production. I'll = rectify this when back in Cambridge with a version of www.openmirage.org that runs on a Cubieboard2. > >=20 > > In the meanwhile, would you be able to test if my point release of tcpi= p.2.3.1 fixes your issue? Do > >=20 > > opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 <> > >=20 > > Once someone with a Cubie2 confirms that the regression has gone, I'll = push this to OPAM. > >=20 > > The mirage-skeleton/static_website works fine for me with that change. >=20 > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with th= e fix. Hmm, I'm now wondering if I've done something completely wrong here. After the re-build with tcpip 2.3.1 I no longer get any asserts, but I also get absolutely nothing in reply on HTTP requests... that wasn't exactly what I expected. I did expect a reply with a bit of HTML. ~~~ output on xen console on ARM Sending DHCP broadcast (length 552) DHCP response: input ciaddr 0.0.0.0 yiaddr 192.168.0.27 siaddr 192.168.0.1 giaddr 0.0.0.0 chaddr 00163e2128a900000000000000000000 sname file=20 DHCP: offer received: 192.168.0.27 DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS servers(83.255.24= 5.11,193.150.193.150), Subnet mask(255.255.255.0), Server identifer(192.168= =2E0.1), Routers(192.168.0.1), Lease time(86400) Sending DHCP broadcast (length 552) DHCP response: input ciaddr 0.0.0.0 yiaddr 192.168.0.27 siaddr 192.168.0.1 giaddr 0.0.0.0 chaddr 00163e2128a900000000000000000000 sname file=20 DHCP: offer received IPv4: 192.168.0.27 Netmask: 255.255.255.0 Gateways: [192.= 168.0.1] sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false ARP: sending gratuitous from 192.168.0.27 DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw [192.168.= 0.1] Manager: configuration done ARP responding to: who-has 192.168.0.27? ARP: transmitting probe -> 192.168.0.11 ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd conn 1 closed conn 2 closed ARP responding to: who-has 192.168.0.27? conn 3 closed conn 4 closed ~~~ ~~~ on my laptop % curl http://192.168.0.27/ ~~~ curl doesn't produce any output, but shortly after invoking it I see a `con= n N closed` on teh Xen console. I'm building as before: ~~~ $ make configure MODE=3Dxen FS=3Dcrunch NET=3Ddirect DHCP=3Dtrue PORT=3D80 =2E.. $ make build ~~~ with the same edits to `src/www.xl` as before (removing MAC, bridge is set = to `xenbr0`). /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus The ultimate goal of all computer science is the program. The performance of programs was once the noblest function of computer science, and computer science was indispensable to great programs. Today, programming and computer science exist in complacent isolation, and can be [rescued only] by conscious co=F6peration and collaboration of all programmers. --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUdpCsACgkQiMWTaatN+6T/TQCdF+9DSVGAeuAKo/nv926Mpykn FcEAn2dYtSe8vGWkFqqErh1Mj9nyXnNb =aPLD -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- --===============4090709698408854979== 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 --===============4090709698408854979==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 02 20:19:07 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Apr 2015 20:19:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdlZq-0006rE-Pi; Thu, 02 Apr 2015 20:18:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YdlZq-0006qm-A5 for mirageos-devel@lists.xenproject.org; Thu, 02 Apr 2015 20:18:58 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 34/5C-23555-134AD155; Thu, 02 Apr 2015 20:18:57 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-4.tower-31.messagelabs.com!1428005936!13477268!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31546 invoked from network); 2 Apr 2015 20:18:56 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2015 20:18:56 -0000 Received: by lagg8 with SMTP id g8so68165501lag.1 for ; Thu, 02 Apr 2015 13:18:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=CkL91RZWQqpBmUtLnmYRI8xWXQmWsf7UQPhhvqTvALw=; b=T+EP8n1ehEJ/SnTNFuwamDflqURSbFT4L9OH2B4CE/ye5lKMaUQEWuFSA8PZqyMVUr ziWzawBMAGhLb0XkdYlQICjeaH4IbUNeRvxX+l0IlLfbJ6dCJ6bfhXI1cttE7QRk8Wfw dCPqm9RPw45j0z6x8yAxrq0kYVkb4hUa3kGEsmZVfeUpu31lT3seGD3X98bft1eOhvMV RBcHM0QUdaz4zWiAMdHrAz1GS8V1KOu2xTlLPuajnosPhu9vGJWn5zasTHfMcHb1L3bC iM/jdr35dFw5kTmKXPhv46ecUePcSfkooXwWrVoZqAivRNjke8tr0jr/nJC1uS+Mo+RX HBlw== X-Gm-Message-State: ALoCoQkKXMLzJQUM2Ykizl4mnc5ZmAcw57MvYk6MgM4k+FIFbb3wljijo4cCHE+Vzp7JAj2Dq4Up X-Received: by 10.112.136.232 with SMTP id qd8mr23706322lbb.1.1428005935849; Thu, 02 Apr 2015 13:18:55 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id t3sm1197519lag.15.2015.04.02.13.18.53 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2015 13:18:54 -0700 (PDT) Date: Thu, 2 Apr 2015 22:18:51 +0200 From: Magnus Therning To: mirageos-devel@lists.xenproject.org Message-ID: <20150402201851.GA10627@tatooine> References: <20150329160245.GA5672@tatooine> <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> MIME-Version: 1.0 In-Reply-To: <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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="===============4090709698408854979==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4090709698408854979== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote: > On 31 Mar 2015, at 21:09, David Scott wrote: > >=20 > >=20 > >=20 > > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy > wrote: > > On 31 Mar 2015, at 07:37, Magnus Therning > wrote: > >>=20 > >> > After a clean rebuild on my cubieboard, I'm getting the assertion fa= ilures too, which is good. I notice the assert that's failing was added rel= atively recently[1] in tcpip v2.2.3 so it's possible that it's simply highl= ighting an old bug in mirage-net-xen. The hunt continues... >>>=20 >>> Ah, that's "good" news indeed. I'll try, but won't make any promises, t= o look a bit at it too. More as a learning exercise then with an aim to act= ually find and fix the issue :) >>>=20 >> Excellent bug report Magnus! We didn't catch this due to the lack of re= gular automated testing on ARM. We would catch this on x86 due to deployin= g our sites regularly, but we don't currently run ARM in production. I'll = rectify this when back in Cambridge with a version of www.openmirage.org that runs on a Cubieboard2. > >=20 > > In the meanwhile, would you be able to test if my point release of tcpi= p.2.3.1 fixes your issue? Do > >=20 > > opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 <> > >=20 > > Once someone with a Cubie2 confirms that the regression has gone, I'll = push this to OPAM. > >=20 > > The mirage-skeleton/static_website works fine for me with that change. >=20 > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with th= e fix. Hmm, I'm now wondering if I've done something completely wrong here. After the re-build with tcpip 2.3.1 I no longer get any asserts, but I also get absolutely nothing in reply on HTTP requests... that wasn't exactly what I expected. I did expect a reply with a bit of HTML. ~~~ output on xen console on ARM Sending DHCP broadcast (length 552) DHCP response: input ciaddr 0.0.0.0 yiaddr 192.168.0.27 siaddr 192.168.0.1 giaddr 0.0.0.0 chaddr 00163e2128a900000000000000000000 sname file=20 DHCP: offer received: 192.168.0.27 DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS servers(83.255.24= 5.11,193.150.193.150), Subnet mask(255.255.255.0), Server identifer(192.168= =2E0.1), Routers(192.168.0.1), Lease time(86400) Sending DHCP broadcast (length 552) DHCP response: input ciaddr 0.0.0.0 yiaddr 192.168.0.27 siaddr 192.168.0.1 giaddr 0.0.0.0 chaddr 00163e2128a900000000000000000000 sname file=20 DHCP: offer received IPv4: 192.168.0.27 Netmask: 255.255.255.0 Gateways: [192.= 168.0.1] sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false ARP: sending gratuitous from 192.168.0.27 DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw [192.168.= 0.1] Manager: configuration done ARP responding to: who-has 192.168.0.27? ARP: transmitting probe -> 192.168.0.11 ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd conn 1 closed conn 2 closed ARP responding to: who-has 192.168.0.27? conn 3 closed conn 4 closed ~~~ ~~~ on my laptop % curl http://192.168.0.27/ ~~~ curl doesn't produce any output, but shortly after invoking it I see a `con= n N closed` on teh Xen console. I'm building as before: ~~~ $ make configure MODE=3Dxen FS=3Dcrunch NET=3Ddirect DHCP=3Dtrue PORT=3D80 =2E.. $ make build ~~~ with the same edits to `src/www.xl` as before (removing MAC, bridge is set = to `xenbr0`). /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus The ultimate goal of all computer science is the program. The performance of programs was once the noblest function of computer science, and computer science was indispensable to great programs. Today, programming and computer science exist in complacent isolation, and can be [rescued only] by conscious co=F6peration and collaboration of all programmers. --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUdpCsACgkQiMWTaatN+6T/TQCdF+9DSVGAeuAKo/nv926Mpykn FcEAn2dYtSe8vGWkFqqErh1Mj9nyXnNb =aPLD -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- --===============4090709698408854979== 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 --===============4090709698408854979==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 02 20:20:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Apr 2015 20:20:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ydlbc-0007dE-Jq; Thu, 02 Apr 2015 20:20:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ydlba-0007cR-L9 for mirageos-devel@lists.xenproject.org; Thu, 02 Apr 2015 20:20:46 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 1C/A5-30165-D94AD155; Thu, 02 Apr 2015 20:20:45 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1428006042!11073653!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18179 invoked from network); 2 Apr 2015 20:20:43 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2015 20:20:43 -0000 Received: by patj18 with SMTP id j18so94378997pat.2 for ; Thu, 02 Apr 2015 13:20:42 -0700 (PDT) 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=rE6AAjIvfrQ6YMMPxHdQl3rP7LSJlWUiZ6CwKbp0/pE=; b=pH6p2KLMVWe1IExoEeSd/iTm0Qmjss2KERK6P2FF2yOML87UNLc5VevmYEXFmLy7CW CejRXnN3UalEsMzGPUfXAKsiXds/Pzgi/kzEO0Yl0zWkwS3aQ3vCXgboer9DX+S0hjWu y5ojO7mdHNbu6o8kbysRqTF0WMtTCD64PUxNqRv8L2zqeFluYAMavc0oJgtjtiAeIG6p jqxEUAzB/8u4MbNKYvjiBjWvnK8l/heVpX6HF3HS6+8srb7G+IDqAbalf5SKnDW56jlU FTmFwIxEn7P3eCAxp2GczRUfpHcXh3fuVLrcy+PrMuBFcuKhFLjD37TmKXuAj3oAmbRP qT/g== MIME-Version: 1.0 X-Received: by 10.70.35.130 with SMTP id h2mr90312017pdj.28.1428006042266; Thu, 02 Apr 2015 13:20:42 -0700 (PDT) Received: by 10.70.102.205 with HTTP; Thu, 2 Apr 2015 13:20:42 -0700 (PDT) In-Reply-To: <20150402201851.GA10627@tatooine> References: <20150329160245.GA5672@tatooine> <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> <20150402201851.GA10627@tatooine> Date: Thu, 2 Apr 2015 21:20:42 +0100 Message-ID: From: David Scott To: Magnus Therning Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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="===============7985489331914458746==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7985489331914458746== Content-Type: multipart/alternative; boundary=047d7bd91738e2f2340512c390a7 --047d7bd91738e2f2340512c390a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning wrote= : > On Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote: > > On 31 Mar 2015, at 21:09, David Scott wrote: > > > > > > > > > > > > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy > wrote: > > > On 31 Mar 2015, at 07:37, Magnus Therning > wrote: > > >> > > >> > After a clean rebuild on my cubieboard, I'm getting the assertion > failures too, which is good. I notice the assert that's failing was added > relatively recently[1] in tcpip v2.2.3 so it's possible that it's simply > highlighting an old bug in mirage-net-xen. The hunt continues... > >>> > >>> Ah, that's "good" news indeed. I'll try, but won't make any promises, > to look a bit at it too. More as a learning exercise then with an aim to > actually find and fix the issue :) > >>> > >> Excellent bug report Magnus! We didn't catch this due to the lack of > regular automated testing on ARM. We would catch this on x86 due to > deploying our sites regularly, but we don't currently run ARM in > production. I'll rectify this when back in Cambridge with a version of > www.openmirage.org that runs on a > Cubieboard2. > > > > > > In the meanwhile, would you be able to test if my point release of > tcpip.2.3.1 fixes your issue? Do > > > > > > opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 <> > > > > > > Once someone with a Cubie2 confirms that the regression has gone, I'l= l > push this to OPAM. > > > > > > The mirage-skeleton/static_website works fine for me with that change= . > > > > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with > the fix. > > Hmm, I'm now wondering if I've done something completely wrong here. > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I > also get absolutely nothing in reply on HTTP requests... that wasn't > exactly what I expected. I did expect a reply with a bit of HTML. > > ~~~ output on xen console on ARM > Sending DHCP broadcast (length 552) > DHCP response: > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > siaddr 192.168.0.1 giaddr 0.0.0.0 > chaddr 00163e2128a900000000000000000000 sname file > DHCP: offer received: 192.168.0.27 > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Serve= r > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400) > Sending DHCP broadcast (length 552) > DHCP response: > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > siaddr 192.168.0.1 giaddr 0.0.0.0 > chaddr 00163e2128a900000000000000000000 sname file > DHCP: offer received > IPv4: 192.168.0.27 > Netmask: 255.255.255.0 > Gateways: > [192.168.0.1] > sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false > ARP: sending gratuitous from 192.168.0.27 > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw > [192.168.0.1] > Manager: configuration done > ARP responding to: who-has 192.168.0.27? > ARP: transmitting probe -> 192.168.0.11 > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd > conn 1 closed > conn 2 closed > ARP responding to: who-has 192.168.0.27? > conn 3 closed > conn 4 closed > ~~~ > > ~~~ on my laptop > % curl http://192.168.0.27/ > ~~~ > > curl doesn't produce any output, but shortly after invoking it I see a > `conn N closed` on teh Xen console. > Could you grab a tcpdump of that and post the .pcap file? Thanks, Dave > > I'm building as before: > > ~~~ > $ make configure MODE=3Dxen FS=3Dcrunch NET=3Ddirect DHCP=3Dtrue PORT=3D8= 0 > ... > $ make build > ~~~ > > with the same edits to `src/www.xl` as before (removing MAC, bridge is se= t > to `xenbr0`). > > /M > > -- > Magnus Therning OpenPGP: 0xAB4DFBA4 > email: magnus@therning.org jabber: magnus@therning.org > twitter: magthe http://therning.org/magnus > > The ultimate goal of all computer science is the program. The > performance of programs was once the noblest function of computer > science, and computer science was indispensable to great programs. > Today, programming and computer science exist in complacent isolation, > and can be [rescued only] by conscious co=C3=B6peration and collaboration > of all programmers. > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --=20 Dave Scott --047d7bd91738e2f2340512c390a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning <<= a href=3D"mailto:magnus@therning.org" target=3D"_blank">magnus@therning.org= > wrote:
O= n Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote:
> On 31 Mar 2015, at 21:09, David Scott <scott.dj@gmail.com> wrote:
> >
> >
> >
> > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy <anil@recoil.org <mailto:anil@recoil.org>> wrote:
> > On 31 Mar 2015, at 07:37, Magnus Therning <magnus@therning.org <mailto:magnus@therning.org>> wrote:<= br> > >>
> >> > After a clean rebuild on my cubieboard, I'm getting = the assertion failures too, which is good. I notice the assert that's f= ailing was added relatively recently[1] in tcpip v2.2.3 so it's possibl= e that it's simply highlighting an old bug in mirage-net-xen. The hunt = continues...
>>>
>>> Ah, that's "good" news indeed. I'll try, but= won't make any promises, to look a bit at it too. More as a learning e= xercise then with an aim to actually find and fix the issue :)
>>>
>> Excellent bug report Magnus!=C2=A0 We didn't catch this= due to the lack of regular automated testing on ARM.=C2=A0 We would catch = this on x86 due to deploying our sites regularly, but we don't currentl= y run ARM in production.=C2=A0 I'll rectify this when back in Cambridge= with a version of = www.openmirage.org <http://www.openmirage.org/> that runs on a Cubieboard2.
> >
> > In the meanwhile, would you be able to test if my point release o= f tcpip.2.3.1 fixes your issue? Do
> >
> >=C2=A0 =C2=A0 =C2=A0opam pin add tcpip git://github.com/mirage/mir= age-tcpip#v2.3.1 <>
> >
> > Once someone with a Cubie2 confirms that the regression has gone,= I'll push this to OPAM.
> >
> > The mirage-skeleton/static_website works fine for me with that ch= ange.
>
> Thanks for confirming!=C2=A0 Tcpip.2.3.1 has now been released to OPAM= with the fix.

Hmm, I'm now wondering if I've done something completely wro= ng here.
After the re-build with tcpip 2.3.1 I no longer get any asserts, but I
also get absolutely nothing in reply on HTTP requests... that wasn't exactly what I expected.=C2=A0 I did expect a reply with a bit of HTML.

~~~ output on xen console on ARM
Sending DHCP broadcast (length 552)
DHCP response:
input ciaddr 0.0.0.0 yiaddr 192.168.0.27
siaddr 192.168.0.1 giaddr 0.0.0.0
chaddr 00163e2128a900000000000000000000 sname=C2=A0 file
DHCP: offer received: 192.168.0.27
DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS servers(83.255.24= 5.11,193.150.193.150), Subnet mask(255.255.255.0), Server identifer(192.168= .0.1), Routers(192.168.0.1), Lease time(86400)
Sending DHCP broadcast (length 552)
DHCP response:
input ciaddr 0.0.0.0 yiaddr 192.168.0.27
siaddr 192.168.0.1 giaddr 0.0.0.0
chaddr 00163e2128a900000000000000000000 sname=C2=A0 file
DHCP: offer received
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IPv4:= 192.168.0.27
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Netmask: 255.255.255.0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Gateways: [1= 92.168.0.1]
=C2=A0sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false ARP: sending gratuitous from 192.168.0.27
DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw [192.168.= 0.1]
Manager: configuration done
ARP responding to: who-has 192.168.0.27?
ARP: transmitting probe -> 192.168.0.11
ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd
conn 1 closed
conn 2 closed
ARP responding to: who-has 192.168.0.27?
conn 3 closed
conn 4 closed
~~~

~~~ on my laptop
% curl http://192.168.0.= 27/
~~~

curl doesn't produce any output, but shortly after invoking it I see a = `conn N closed` on teh Xen console.

Cou= ld you grab a tcpdump of that and post the .pcap file?

=
Thanks,
Dave
=C2=A0

I'm building as before:

~~~
$ make configure MODE=3Dxen FS=3Dcrunch NET=3Ddirect DHCP=3Dtrue PORT=3D80<= br> ...
$ make build
~~~

with the same edits to `src/www.xl` as before (removing MAC, bridge is set = to `xenbr0`).

/M

--
Magnus Therning=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 OpenPGP: 0xAB4DFBA4
email: magnus@therning.org=C2=A0= =C2=A0jabber: magnus@therning.org
twitter: magthe=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://therning.org/mag= nus

The ultimate goal of all com= puter science is the program.=C2=A0 The
performance of programs was once the noblest function of computer
science, and computer science was indispensable to great programs.
Today, programming and computer science exist in complacent isolation,
and can be [rescued only] by conscious co=C3=B6peration and collaboration of all programmers.

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




--
Dave Scott
--047d7bd91738e2f2340512c390a7-- --===============7985489331914458746== 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 --===============7985489331914458746==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 02 20:20:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Apr 2015 20:20:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ydlbc-0007dE-Jq; Thu, 02 Apr 2015 20:20:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ydlba-0007cR-L9 for mirageos-devel@lists.xenproject.org; Thu, 02 Apr 2015 20:20:46 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 1C/A5-30165-D94AD155; Thu, 02 Apr 2015 20:20:45 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1428006042!11073653!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18179 invoked from network); 2 Apr 2015 20:20:43 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2015 20:20:43 -0000 Received: by patj18 with SMTP id j18so94378997pat.2 for ; Thu, 02 Apr 2015 13:20:42 -0700 (PDT) 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=rE6AAjIvfrQ6YMMPxHdQl3rP7LSJlWUiZ6CwKbp0/pE=; b=pH6p2KLMVWe1IExoEeSd/iTm0Qmjss2KERK6P2FF2yOML87UNLc5VevmYEXFmLy7CW CejRXnN3UalEsMzGPUfXAKsiXds/Pzgi/kzEO0Yl0zWkwS3aQ3vCXgboer9DX+S0hjWu y5ojO7mdHNbu6o8kbysRqTF0WMtTCD64PUxNqRv8L2zqeFluYAMavc0oJgtjtiAeIG6p jqxEUAzB/8u4MbNKYvjiBjWvnK8l/heVpX6HF3HS6+8srb7G+IDqAbalf5SKnDW56jlU FTmFwIxEn7P3eCAxp2GczRUfpHcXh3fuVLrcy+PrMuBFcuKhFLjD37TmKXuAj3oAmbRP qT/g== MIME-Version: 1.0 X-Received: by 10.70.35.130 with SMTP id h2mr90312017pdj.28.1428006042266; Thu, 02 Apr 2015 13:20:42 -0700 (PDT) Received: by 10.70.102.205 with HTTP; Thu, 2 Apr 2015 13:20:42 -0700 (PDT) In-Reply-To: <20150402201851.GA10627@tatooine> References: <20150329160245.GA5672@tatooine> <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> <20150402201851.GA10627@tatooine> Date: Thu, 2 Apr 2015 21:20:42 +0100 Message-ID: From: David Scott To: Magnus Therning Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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="===============7985489331914458746==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7985489331914458746== Content-Type: multipart/alternative; boundary=047d7bd91738e2f2340512c390a7 --047d7bd91738e2f2340512c390a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning wrote= : > On Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote: > > On 31 Mar 2015, at 21:09, David Scott wrote: > > > > > > > > > > > > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy > wrote: > > > On 31 Mar 2015, at 07:37, Magnus Therning > wrote: > > >> > > >> > After a clean rebuild on my cubieboard, I'm getting the assertion > failures too, which is good. I notice the assert that's failing was added > relatively recently[1] in tcpip v2.2.3 so it's possible that it's simply > highlighting an old bug in mirage-net-xen. The hunt continues... > >>> > >>> Ah, that's "good" news indeed. I'll try, but won't make any promises, > to look a bit at it too. More as a learning exercise then with an aim to > actually find and fix the issue :) > >>> > >> Excellent bug report Magnus! We didn't catch this due to the lack of > regular automated testing on ARM. We would catch this on x86 due to > deploying our sites regularly, but we don't currently run ARM in > production. I'll rectify this when back in Cambridge with a version of > www.openmirage.org that runs on a > Cubieboard2. > > > > > > In the meanwhile, would you be able to test if my point release of > tcpip.2.3.1 fixes your issue? Do > > > > > > opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 <> > > > > > > Once someone with a Cubie2 confirms that the regression has gone, I'l= l > push this to OPAM. > > > > > > The mirage-skeleton/static_website works fine for me with that change= . > > > > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with > the fix. > > Hmm, I'm now wondering if I've done something completely wrong here. > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I > also get absolutely nothing in reply on HTTP requests... that wasn't > exactly what I expected. I did expect a reply with a bit of HTML. > > ~~~ output on xen console on ARM > Sending DHCP broadcast (length 552) > DHCP response: > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > siaddr 192.168.0.1 giaddr 0.0.0.0 > chaddr 00163e2128a900000000000000000000 sname file > DHCP: offer received: 192.168.0.27 > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Serve= r > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400) > Sending DHCP broadcast (length 552) > DHCP response: > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > siaddr 192.168.0.1 giaddr 0.0.0.0 > chaddr 00163e2128a900000000000000000000 sname file > DHCP: offer received > IPv4: 192.168.0.27 > Netmask: 255.255.255.0 > Gateways: > [192.168.0.1] > sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false > ARP: sending gratuitous from 192.168.0.27 > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw > [192.168.0.1] > Manager: configuration done > ARP responding to: who-has 192.168.0.27? > ARP: transmitting probe -> 192.168.0.11 > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd > conn 1 closed > conn 2 closed > ARP responding to: who-has 192.168.0.27? > conn 3 closed > conn 4 closed > ~~~ > > ~~~ on my laptop > % curl http://192.168.0.27/ > ~~~ > > curl doesn't produce any output, but shortly after invoking it I see a > `conn N closed` on teh Xen console. > Could you grab a tcpdump of that and post the .pcap file? Thanks, Dave > > I'm building as before: > > ~~~ > $ make configure MODE=3Dxen FS=3Dcrunch NET=3Ddirect DHCP=3Dtrue PORT=3D8= 0 > ... > $ make build > ~~~ > > with the same edits to `src/www.xl` as before (removing MAC, bridge is se= t > to `xenbr0`). > > /M > > -- > Magnus Therning OpenPGP: 0xAB4DFBA4 > email: magnus@therning.org jabber: magnus@therning.org > twitter: magthe http://therning.org/magnus > > The ultimate goal of all computer science is the program. The > performance of programs was once the noblest function of computer > science, and computer science was indispensable to great programs. > Today, programming and computer science exist in complacent isolation, > and can be [rescued only] by conscious co=C3=B6peration and collaboration > of all programmers. > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --=20 Dave Scott --047d7bd91738e2f2340512c390a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning <<= a href=3D"mailto:magnus@therning.org" target=3D"_blank">magnus@therning.org= > wrote:
O= n Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote:
> On 31 Mar 2015, at 21:09, David Scott <scott.dj@gmail.com> wrote:
> >
> >
> >
> > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy <anil@recoil.org <mailto:anil@recoil.org>> wrote:
> > On 31 Mar 2015, at 07:37, Magnus Therning <magnus@therning.org <mailto:magnus@therning.org>> wrote:<= br> > >>
> >> > After a clean rebuild on my cubieboard, I'm getting = the assertion failures too, which is good. I notice the assert that's f= ailing was added relatively recently[1] in tcpip v2.2.3 so it's possibl= e that it's simply highlighting an old bug in mirage-net-xen. The hunt = continues...
>>>
>>> Ah, that's "good" news indeed. I'll try, but= won't make any promises, to look a bit at it too. More as a learning e= xercise then with an aim to actually find and fix the issue :)
>>>
>> Excellent bug report Magnus!=C2=A0 We didn't catch this= due to the lack of regular automated testing on ARM.=C2=A0 We would catch = this on x86 due to deploying our sites regularly, but we don't currentl= y run ARM in production.=C2=A0 I'll rectify this when back in Cambridge= with a version of = www.openmirage.org <http://www.openmirage.org/> that runs on a Cubieboard2.
> >
> > In the meanwhile, would you be able to test if my point release o= f tcpip.2.3.1 fixes your issue? Do
> >
> >=C2=A0 =C2=A0 =C2=A0opam pin add tcpip git://github.com/mirage/mir= age-tcpip#v2.3.1 <>
> >
> > Once someone with a Cubie2 confirms that the regression has gone,= I'll push this to OPAM.
> >
> > The mirage-skeleton/static_website works fine for me with that ch= ange.
>
> Thanks for confirming!=C2=A0 Tcpip.2.3.1 has now been released to OPAM= with the fix.

Hmm, I'm now wondering if I've done something completely wro= ng here.
After the re-build with tcpip 2.3.1 I no longer get any asserts, but I
also get absolutely nothing in reply on HTTP requests... that wasn't exactly what I expected.=C2=A0 I did expect a reply with a bit of HTML.

~~~ output on xen console on ARM
Sending DHCP broadcast (length 552)
DHCP response:
input ciaddr 0.0.0.0 yiaddr 192.168.0.27
siaddr 192.168.0.1 giaddr 0.0.0.0
chaddr 00163e2128a900000000000000000000 sname=C2=A0 file
DHCP: offer received: 192.168.0.27
DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS servers(83.255.24= 5.11,193.150.193.150), Subnet mask(255.255.255.0), Server identifer(192.168= .0.1), Routers(192.168.0.1), Lease time(86400)
Sending DHCP broadcast (length 552)
DHCP response:
input ciaddr 0.0.0.0 yiaddr 192.168.0.27
siaddr 192.168.0.1 giaddr 0.0.0.0
chaddr 00163e2128a900000000000000000000 sname=C2=A0 file
DHCP: offer received
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IPv4:= 192.168.0.27
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Netmask: 255.255.255.0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Gateways: [1= 92.168.0.1]
=C2=A0sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false ARP: sending gratuitous from 192.168.0.27
DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw [192.168.= 0.1]
Manager: configuration done
ARP responding to: who-has 192.168.0.27?
ARP: transmitting probe -> 192.168.0.11
ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd
conn 1 closed
conn 2 closed
ARP responding to: who-has 192.168.0.27?
conn 3 closed
conn 4 closed
~~~

~~~ on my laptop
% curl http://192.168.0.= 27/
~~~

curl doesn't produce any output, but shortly after invoking it I see a = `conn N closed` on teh Xen console.

Cou= ld you grab a tcpdump of that and post the .pcap file?

=
Thanks,
Dave
=C2=A0

I'm building as before:

~~~
$ make configure MODE=3Dxen FS=3Dcrunch NET=3Ddirect DHCP=3Dtrue PORT=3D80<= br> ...
$ make build
~~~

with the same edits to `src/www.xl` as before (removing MAC, bridge is set = to `xenbr0`).

/M

--
Magnus Therning=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 OpenPGP: 0xAB4DFBA4
email: magnus@therning.org=C2=A0= =C2=A0jabber: magnus@therning.org
twitter: magthe=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://therning.org/mag= nus

The ultimate goal of all com= puter science is the program.=C2=A0 The
performance of programs was once the noblest function of computer
science, and computer science was indispensable to great programs.
Today, programming and computer science exist in complacent isolation,
and can be [rescued only] by conscious co=C3=B6peration and collaboration of all programmers.

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




--
Dave Scott
--047d7bd91738e2f2340512c390a7-- --===============7985489331914458746== 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 --===============7985489331914458746==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 02 20:32:44 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Apr 2015 20:32: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 1Ydln9-0002Zb-S5; Thu, 02 Apr 2015 20:32:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ydln8-0002ZU-Fr for mirageos-devel@lists.xenproject.org; Thu, 02 Apr 2015 20:32:42 +0000 Received: from [193.109.254.147] by server-11.bemta-14.messagelabs.com id 9A/3A-22533-967AD155; Thu, 02 Apr 2015 20:32:41 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1428006759!11949494!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2215 invoked from network); 2 Apr 2015 20:32:40 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2015 20:32:40 -0000 Received: by lboc7 with SMTP id c7so67427360lbo.1 for ; Thu, 02 Apr 2015 13:32:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=MTW+UTMb2xxZcBuKiKpku8V0ql8KaxNtbWdcaiZBFJM=; b=BDKtp6bRYVjERBd7U0MxfUr0u2tq3P7hGIdlZtOuj4UQY4ufryCCyuj+BDbBTKxlkB wXm/IIjI0YH/j54+02l3Pv7rVUKJIGJ3qhHYcR/pyNn+aJuFNLWtyQOiGsxZrfjhVI88 THdjmArq5l/aYyCgfCAaf0B10g4Fz67evvPN7sQmVIUtOncXNKXOkWQMaDWv6GG5DCVs tTWOnTwLdtEtCwUyPcCtYPIAdRZW3k9H0I5WSRUqFVXqSRSEEk4zt5gFuuz6reZfng/W 3JvzZGQcVTq5OlLpwvBN1RnpLCn8LBAu5OTUP57DZJ9lZ5ov120KBHGce1wAmlL+Zc8W wxMg== X-Gm-Message-State: ALoCoQm6LZqFV5ngC8aV9eIjcpkPNupXgCEnCiiPvZKCn2Umj/YKUBYLRjHkbU+/eGZV1riBgKCg X-Received: by 10.112.160.165 with SMTP id xl5mr42582875lbb.109.1428006759301; Thu, 02 Apr 2015 13:32:39 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id tj10sm1201381lbb.4.2015.04.02.13.32.37 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2015 13:32:38 -0700 (PDT) Date: Thu, 2 Apr 2015 22:32:35 +0200 From: Magnus Therning To: David Scott Message-ID: <20150402203235.GB10627@tatooine> References: <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> <20150402201851.GA10627@tatooine> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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="===============4263830175070234380==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4263830175070234380== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZwgA9U+XZDXt4+m+" Content-Disposition: inline --ZwgA9U+XZDXt4+m+ Content-Type: multipart/mixed; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 02, 2015 at 09:20:42PM +0100, David Scott wrote: > On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning wro= te: >=20 > > On Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote: > > > On 31 Mar 2015, at 21:09, David Scott wrote: > > > > > > > > > > > > > > > > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy > > wrote: > > > > On 31 Mar 2015, at 07:37, Magnus Therning > > wrote: > > > >> > > > >> > After a clean rebuild on my cubieboard, I'm getting the assertion > > failures too, which is good. I notice the assert that's failing was add= ed > > relatively recently[1] in tcpip v2.2.3 so it's possible that it's simply > > highlighting an old bug in mirage-net-xen. The hunt continues... > > >>> > > >>> Ah, that's "good" news indeed. I'll try, but won't make any promise= s, > > to look a bit at it too. More as a learning exercise then with an aim to > > actually find and fix the issue :) > > >>> > > >> Excellent bug report Magnus! We didn't catch this due to the lack of > > regular automated testing on ARM. We would catch this on x86 due to > > deploying our sites regularly, but we don't currently run ARM in > > production. I'll rectify this when back in Cambridge with a version of > > www.openmirage.org that runs on a > > Cubieboard2. > > > > > > > > In the meanwhile, would you be able to test if my point release of > > tcpip.2.3.1 fixes your issue? Do > > > > > > > > opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 = <> > > > > > > > > Once someone with a Cubie2 confirms that the regression has gone, I= 'll > > push this to OPAM. > > > > > > > > The mirage-skeleton/static_website works fine for me with that chan= ge. > > > > > > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with > > the fix. > > > > Hmm, I'm now wondering if I've done something completely wrong here. > > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I > > also get absolutely nothing in reply on HTTP requests... that wasn't > > exactly what I expected. I did expect a reply with a bit of HTML. > > > > ~~~ output on xen console on ARM > > Sending DHCP broadcast (length 552) > > DHCP response: > > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > > siaddr 192.168.0.1 giaddr 0.0.0.0 > > chaddr 00163e2128a900000000000000000000 sname file > > DHCP: offer received: 192.168.0.27 > > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS > > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Ser= ver > > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400) > > Sending DHCP broadcast (length 552) > > DHCP response: > > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > > siaddr 192.168.0.1 giaddr 0.0.0.0 > > chaddr 00163e2128a900000000000000000000 sname file > > DHCP: offer received > > IPv4: 192.168.0.27 > > Netmask: 255.255.255.0 > > Gateways: > > [192.168.0.1] > > sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false > > ARP: sending gratuitous from 192.168.0.27 > > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw > > [192.168.0.1] > > Manager: configuration done > > ARP responding to: who-has 192.168.0.27? > > ARP: transmitting probe -> 192.168.0.11 > > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd > > conn 1 closed > > conn 2 closed > > ARP responding to: who-has 192.168.0.27? > > conn 3 closed > > conn 4 closed > > ~~~ > > > > ~~~ on my laptop > > % curl http://192.168.0.27/ > > ~~~ > > > > curl doesn't produce any output, but shortly after invoking it I see a > > `conn N closed` on teh Xen console. > > >=20 > Could you grab a tcpdump of that and post the .pcap file? I've attached it, and put it on my Dropbox just in case the list doesn't like attachments. https://www.dropbox.com/s/u0zoeciy6t30sjz/arm-xen-www.pcap?dl=3D0 It's captured using `tcpdump -w arm-xen-www.pcap host 192.168.0.27`. Let me know you need me to re-capture with some other switches on. /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus In order to understand recursion you must first understand recursion. --BwCQnh7xodEAoBMC Content-Type: application/vnd.tcpdump.pcap Content-Disposition: attachment; filename="arm-xen-www.pcap" Content-Transfer-Encoding: base64 1MOyoQIABAAAAAAAAAAAAAAABAABAAAARKYdVb9WBQBKAAAASgAAAAAWPiEoqQDCxg9y3QgA RQAAPPxfQABABrzlwKgAC8CoABvRagBQ6bAyrAAAAACgAnIQlzIAAAIEBbQEAggKADvO8wAA AAABAwMHRKYdVXVrBQA+AAAAPgAAAADCxg9y3QAWPiEoqQgARQAAMKCiAAAmBnKvwKgAG8Co AAsAUNFqGv70VumwMq1wEv//AysAAAIEBbQDAwMARKYdVbVrBQA2AAAANgAAAAAWPiEoqQDC xg9y3QgARQAAKPxgQABABrz4wKgAC8CoABvRagBQ6bAyrRr+9FdQEADlMAoAAESmHVX9awUA ggAAAIIAAAAAFj4hKKkAwsYPct0IAEUAAHT8YUAAQAa8q8CoAAvAqAAb0WoAUOmwMq0a/vRX UBgA5eGLAABHRVQgLyBIVFRQLzEuMQ0KVXNlci1BZ2VudDogY3VybC83LjQxLjANCkhvc3Q6 IDE5Mi4xNjguMC4yNw0KQWNjZXB0OiAqLyoNCg0KRKYdVe5xBQA8AAAAPAAAAADCxg9y3QAW PiEoqQgARQAAKO60AAAmBiSlwKgAG8CoAAsAUNFqGv70V+mwMrNQEP//MOkAAAAAAAAAAESm HVUQcgUAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAAChNzQAAJgbFjMCoABvAqAALAFDRahr+ 9FfpsDKzUBD//zDpAAAAAAAAAABEph1V0IYIAHwAAAB8AAAAABY+ISipAMLGD3LdCABFAABu /GJAAEAGvLDAqAALwKgAG9FqAFDpsDKzGv70V1AYAOWsEQAASFRUUC8xLjENClVzZXItQWdl bnQ6IGN1cmwvNy40MS4wDQpIb3N0OiAxOTIuMTY4LjAuMjcNCkFjY2VwdDogKi8qDQoNCkSm HVWBjQgAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAACjUnQAAJgY+vMCoABvAqAALAFDRahr+ 9FfpsDL5UBD//zCjAAAAAAAAAABOph1V8K4KADYAAAA2AAAAABY+ISipAMLGD3LdCABFAAAo /GNAAEAGvPXAqAALwKgAG9FqAFDpsDL5Gv70V1ARAOUvvQAATqYdVeq4CgA8AAAAPAAAAADC xg9y3QAWPiEoqQgARQAAKK2HAAAmBmXSwKgAG8CoAAsAUNFqGv70V+mwMwBQEP/9MJ4AAAAA AAAAAE6mHVUduQoAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAACj8GQAAJgYXQMCoABvAqAAL AFDRahr+9FfpsDMAUBD//TCeAAAAAAAAAABPph1VBbYBADYAAAA2AAAAABY+ISipAMLGD3Ld CABFAAAo/GRAAEAGvPTAqAALwKgAG9FqAFDpsDL5Gv70V1ARAOUvvQAAT6YdVZ67AQA8AAAA PAAAAADCxg9y3QAWPiEoqQgARQAAKDjEAAAmBtqVwKgAG8CoAAsAUNFqGv70V+mwMwBQEP/9 MJ4AAAAAAAAAAE+mHVUdUw4ANgAAADYAAAAAFj4hKKkAwsYPct0IAEUAACj8ZUAAQAa888Co AAvAqAAb0WoAUOmwMvka/vRXUBEA5S+9AABPph1V2VoOADwAAAA8AAAAAMLGD3LdABY+ISip CABFAAAodccAACYGnZLAqAAbwKgACwBQ0Woa/vRX6bAzAFAQ//0wngAAAAAAAAAAUaYdVS4W CQA2AAAANgAAAAAWPiEoqQDCxg9y3QgARQAAKPxmQABABrzywKgAC8CoABvRagBQ6bAy+Rr+ 9FdQEQDlL70AAFGmHVXsGwkAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAACghKAAAJgbyMcCo ABvAqAALAFDRahr+9FfpsDMAUBD//TCeAAAAAAAAAABUph1V/eoNADYAAAA2AAAAABY+ISip AMLGD3LdCABFAAAo/GdAAEAGvPHAqAALwKgAG9FqAFDpsDL5Gv70V1ARAOUvvQAAVKYdVbjw DQA8AAAAPAAAAADCxg9y3QAWPiEoqQgARQAAKOJcAAAmBjD9wKgAG8CoAAsAUNFqGv70V+mw MwBQEP/9MJ4AAAAAAAAAAFumHVWeOAgANgAAADYAAAAAFj4hKKkAwsYPct0IAEUAACj8aEAA QAa88MCoAAvAqAAb0WoAUOmwMvka/vRXUBEA5S+9AABbph1V1VUIADwAAAA8AAAAAMLGD3Ld ABY+ISipCABFAAAon50AACYGc7zAqAAbwKgACwBQ0Woa/vRX6bAzAFAQ//0wngAAAAAAAAAA --BwCQnh7xodEAoBMC-- --ZwgA9U+XZDXt4+m+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUdp2MACgkQiMWTaatN+6Q9XQCfSmGhlc0lyS7zuvqSMyV6THn5 PU4AoNzqR0SQSvJYwThjaLxvXQynTUic =ateL -----END PGP SIGNATURE----- --ZwgA9U+XZDXt4+m+-- --===============4263830175070234380== 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 --===============4263830175070234380==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 02 20:32:44 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Apr 2015 20:32: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 1Ydln9-0002Zb-S5; Thu, 02 Apr 2015 20:32:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ydln8-0002ZU-Fr for mirageos-devel@lists.xenproject.org; Thu, 02 Apr 2015 20:32:42 +0000 Received: from [193.109.254.147] by server-11.bemta-14.messagelabs.com id 9A/3A-22533-967AD155; Thu, 02 Apr 2015 20:32:41 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1428006759!11949494!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2215 invoked from network); 2 Apr 2015 20:32:40 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2015 20:32:40 -0000 Received: by lboc7 with SMTP id c7so67427360lbo.1 for ; Thu, 02 Apr 2015 13:32:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=MTW+UTMb2xxZcBuKiKpku8V0ql8KaxNtbWdcaiZBFJM=; b=BDKtp6bRYVjERBd7U0MxfUr0u2tq3P7hGIdlZtOuj4UQY4ufryCCyuj+BDbBTKxlkB wXm/IIjI0YH/j54+02l3Pv7rVUKJIGJ3qhHYcR/pyNn+aJuFNLWtyQOiGsxZrfjhVI88 THdjmArq5l/aYyCgfCAaf0B10g4Fz67evvPN7sQmVIUtOncXNKXOkWQMaDWv6GG5DCVs tTWOnTwLdtEtCwUyPcCtYPIAdRZW3k9H0I5WSRUqFVXqSRSEEk4zt5gFuuz6reZfng/W 3JvzZGQcVTq5OlLpwvBN1RnpLCn8LBAu5OTUP57DZJ9lZ5ov120KBHGce1wAmlL+Zc8W wxMg== X-Gm-Message-State: ALoCoQm6LZqFV5ngC8aV9eIjcpkPNupXgCEnCiiPvZKCn2Umj/YKUBYLRjHkbU+/eGZV1riBgKCg X-Received: by 10.112.160.165 with SMTP id xl5mr42582875lbb.109.1428006759301; Thu, 02 Apr 2015 13:32:39 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id tj10sm1201381lbb.4.2015.04.02.13.32.37 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2015 13:32:38 -0700 (PDT) Date: Thu, 2 Apr 2015 22:32:35 +0200 From: Magnus Therning To: David Scott Message-ID: <20150402203235.GB10627@tatooine> References: <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> <20150402201851.GA10627@tatooine> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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="===============4263830175070234380==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4263830175070234380== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZwgA9U+XZDXt4+m+" Content-Disposition: inline --ZwgA9U+XZDXt4+m+ Content-Type: multipart/mixed; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 02, 2015 at 09:20:42PM +0100, David Scott wrote: > On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning wro= te: >=20 > > On Tue, Mar 31, 2015 at 09:49:28PM +0100, Anil Madhavapeddy wrote: > > > On 31 Mar 2015, at 21:09, David Scott wrote: > > > > > > > > > > > > > > > > On Tue, Mar 31, 2015 at 6:43 PM, Anil Madhavapeddy > > wrote: > > > > On 31 Mar 2015, at 07:37, Magnus Therning > > wrote: > > > >> > > > >> > After a clean rebuild on my cubieboard, I'm getting the assertion > > failures too, which is good. I notice the assert that's failing was add= ed > > relatively recently[1] in tcpip v2.2.3 so it's possible that it's simply > > highlighting an old bug in mirage-net-xen. The hunt continues... > > >>> > > >>> Ah, that's "good" news indeed. I'll try, but won't make any promise= s, > > to look a bit at it too. More as a learning exercise then with an aim to > > actually find and fix the issue :) > > >>> > > >> Excellent bug report Magnus! We didn't catch this due to the lack of > > regular automated testing on ARM. We would catch this on x86 due to > > deploying our sites regularly, but we don't currently run ARM in > > production. I'll rectify this when back in Cambridge with a version of > > www.openmirage.org that runs on a > > Cubieboard2. > > > > > > > > In the meanwhile, would you be able to test if my point release of > > tcpip.2.3.1 fixes your issue? Do > > > > > > > > opam pin add tcpip git://github.com/mirage/mirage-tcpip#v2.3.1 = <> > > > > > > > > Once someone with a Cubie2 confirms that the regression has gone, I= 'll > > push this to OPAM. > > > > > > > > The mirage-skeleton/static_website works fine for me with that chan= ge. > > > > > > Thanks for confirming! Tcpip.2.3.1 has now been released to OPAM with > > the fix. > > > > Hmm, I'm now wondering if I've done something completely wrong here. > > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I > > also get absolutely nothing in reply on HTTP requests... that wasn't > > exactly what I expected. I did expect a reply with a bit of HTML. > > > > ~~~ output on xen console on ARM > > Sending DHCP broadcast (length 552) > > DHCP response: > > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > > siaddr 192.168.0.1 giaddr 0.0.0.0 > > chaddr 00163e2128a900000000000000000000 sname file > > DHCP: offer received: 192.168.0.27 > > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS > > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Ser= ver > > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400) > > Sending DHCP broadcast (length 552) > > DHCP response: > > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 > > siaddr 192.168.0.1 giaddr 0.0.0.0 > > chaddr 00163e2128a900000000000000000000 sname file > > DHCP: offer received > > IPv4: 192.168.0.27 > > Netmask: 255.255.255.0 > > Gateways: > > [192.168.0.1] > > sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false > > ARP: sending gratuitous from 192.168.0.27 > > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw > > [192.168.0.1] > > Manager: configuration done > > ARP responding to: who-has 192.168.0.27? > > ARP: transmitting probe -> 192.168.0.11 > > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd > > conn 1 closed > > conn 2 closed > > ARP responding to: who-has 192.168.0.27? > > conn 3 closed > > conn 4 closed > > ~~~ > > > > ~~~ on my laptop > > % curl http://192.168.0.27/ > > ~~~ > > > > curl doesn't produce any output, but shortly after invoking it I see a > > `conn N closed` on teh Xen console. > > >=20 > Could you grab a tcpdump of that and post the .pcap file? I've attached it, and put it on my Dropbox just in case the list doesn't like attachments. https://www.dropbox.com/s/u0zoeciy6t30sjz/arm-xen-www.pcap?dl=3D0 It's captured using `tcpdump -w arm-xen-www.pcap host 192.168.0.27`. Let me know you need me to re-capture with some other switches on. /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus In order to understand recursion you must first understand recursion. --BwCQnh7xodEAoBMC Content-Type: application/vnd.tcpdump.pcap Content-Disposition: attachment; filename="arm-xen-www.pcap" Content-Transfer-Encoding: base64 1MOyoQIABAAAAAAAAAAAAAAABAABAAAARKYdVb9WBQBKAAAASgAAAAAWPiEoqQDCxg9y3QgA RQAAPPxfQABABrzlwKgAC8CoABvRagBQ6bAyrAAAAACgAnIQlzIAAAIEBbQEAggKADvO8wAA AAABAwMHRKYdVXVrBQA+AAAAPgAAAADCxg9y3QAWPiEoqQgARQAAMKCiAAAmBnKvwKgAG8Co AAsAUNFqGv70VumwMq1wEv//AysAAAIEBbQDAwMARKYdVbVrBQA2AAAANgAAAAAWPiEoqQDC xg9y3QgARQAAKPxgQABABrz4wKgAC8CoABvRagBQ6bAyrRr+9FdQEADlMAoAAESmHVX9awUA ggAAAIIAAAAAFj4hKKkAwsYPct0IAEUAAHT8YUAAQAa8q8CoAAvAqAAb0WoAUOmwMq0a/vRX UBgA5eGLAABHRVQgLyBIVFRQLzEuMQ0KVXNlci1BZ2VudDogY3VybC83LjQxLjANCkhvc3Q6 IDE5Mi4xNjguMC4yNw0KQWNjZXB0OiAqLyoNCg0KRKYdVe5xBQA8AAAAPAAAAADCxg9y3QAW PiEoqQgARQAAKO60AAAmBiSlwKgAG8CoAAsAUNFqGv70V+mwMrNQEP//MOkAAAAAAAAAAESm HVUQcgUAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAAChNzQAAJgbFjMCoABvAqAALAFDRahr+ 9FfpsDKzUBD//zDpAAAAAAAAAABEph1V0IYIAHwAAAB8AAAAABY+ISipAMLGD3LdCABFAABu /GJAAEAGvLDAqAALwKgAG9FqAFDpsDKzGv70V1AYAOWsEQAASFRUUC8xLjENClVzZXItQWdl bnQ6IGN1cmwvNy40MS4wDQpIb3N0OiAxOTIuMTY4LjAuMjcNCkFjY2VwdDogKi8qDQoNCkSm HVWBjQgAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAACjUnQAAJgY+vMCoABvAqAALAFDRahr+ 9FfpsDL5UBD//zCjAAAAAAAAAABOph1V8K4KADYAAAA2AAAAABY+ISipAMLGD3LdCABFAAAo /GNAAEAGvPXAqAALwKgAG9FqAFDpsDL5Gv70V1ARAOUvvQAATqYdVeq4CgA8AAAAPAAAAADC xg9y3QAWPiEoqQgARQAAKK2HAAAmBmXSwKgAG8CoAAsAUNFqGv70V+mwMwBQEP/9MJ4AAAAA AAAAAE6mHVUduQoAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAACj8GQAAJgYXQMCoABvAqAAL AFDRahr+9FfpsDMAUBD//TCeAAAAAAAAAABPph1VBbYBADYAAAA2AAAAABY+ISipAMLGD3Ld CABFAAAo/GRAAEAGvPTAqAALwKgAG9FqAFDpsDL5Gv70V1ARAOUvvQAAT6YdVZ67AQA8AAAA PAAAAADCxg9y3QAWPiEoqQgARQAAKDjEAAAmBtqVwKgAG8CoAAsAUNFqGv70V+mwMwBQEP/9 MJ4AAAAAAAAAAE+mHVUdUw4ANgAAADYAAAAAFj4hKKkAwsYPct0IAEUAACj8ZUAAQAa888Co AAvAqAAb0WoAUOmwMvka/vRXUBEA5S+9AABPph1V2VoOADwAAAA8AAAAAMLGD3LdABY+ISip CABFAAAodccAACYGnZLAqAAbwKgACwBQ0Woa/vRX6bAzAFAQ//0wngAAAAAAAAAAUaYdVS4W CQA2AAAANgAAAAAWPiEoqQDCxg9y3QgARQAAKPxmQABABrzywKgAC8CoABvRagBQ6bAy+Rr+ 9FdQEQDlL70AAFGmHVXsGwkAPAAAADwAAAAAwsYPct0AFj4hKKkIAEUAACghKAAAJgbyMcCo ABvAqAALAFDRahr+9FfpsDMAUBD//TCeAAAAAAAAAABUph1V/eoNADYAAAA2AAAAABY+ISip AMLGD3LdCABFAAAo/GdAAEAGvPHAqAALwKgAG9FqAFDpsDL5Gv70V1ARAOUvvQAAVKYdVbjw DQA8AAAAPAAAAADCxg9y3QAWPiEoqQgARQAAKOJcAAAmBjD9wKgAG8CoAAsAUNFqGv70V+mw MwBQEP/9MJ4AAAAAAAAAAFumHVWeOAgANgAAADYAAAAAFj4hKKkAwsYPct0IAEUAACj8aEAA QAa88MCoAAvAqAAb0WoAUOmwMvka/vRXUBEA5S+9AABbph1V1VUIADwAAAA8AAAAAMLGD3Ld ABY+ISipCABFAAAon50AACYGc7zAqAAbwKgACwBQ0Woa/vRX6bAzAFAQ//0wngAAAAAAAAAA --BwCQnh7xodEAoBMC-- --ZwgA9U+XZDXt4+m+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUdp2MACgkQiMWTaatN+6Q9XQCfSmGhlc0lyS7zuvqSMyV6THn5 PU4AoNzqR0SQSvJYwThjaLxvXQynTUic =ateL -----END PGP SIGNATURE----- --ZwgA9U+XZDXt4+m+-- --===============4263830175070234380== 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 --===============4263830175070234380==-- From mirageos-devel-bounces@lists.xenproject.org Fri Apr 03 15:00:39 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Apr 2015 15:00: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 1Ye35D-00014o-Ji; Fri, 03 Apr 2015 15:00:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ye35D-00014c-01 for mirageos-devel@lists.xenproject.org; Fri, 03 Apr 2015 15:00:31 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id F7/45-22343-E0BAE155; Fri, 03 Apr 2015 15:00:30 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-21.messagelabs.com!1428073229!374171!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.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6746 invoked from network); 3 Apr 2015 15:00:29 -0000 Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk) (131.111.8.142) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Apr 2015 15:00:29 -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]:55929 helo=[192.168.0.33]) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Ye35B-0004ew-7b (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Fri, 03 Apr 2015 16:00:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <0D4916D8-8B16-404B-AD07-17473BE64D6E@cam.ac.uk> Date: Fri, 3 Apr 2015 16:00:30 +0100 Message-Id: <8D620BFF-88F8-48BA-A6E0-3BF7A6141B7A@cam.ac.uk> References: <0D4916D8-8B16-404B-AD07-17473BE64D6E@cam.ac.uk> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] End-to-end deployments of unikernels 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, I've posted a follow up to my earlier post, which is more about extrapolating from the tools we have now. A lot of it is speculative and considers how we might use things like Jitsu and Irmin to create demand-driven, hyper-elastic clouds. It's about a 10min read and occasionally refers to the previous post (linked down-thread). http://amirchaudhry.com/heroku-for-unikernels-pt2/ I'd be very interested to hear any feedback. Best wishes, Amir On 31 Mar 2015, at 16:11, Amir Chaudhry wrote: > Hi folks, > > I've published a post that describes the automated, end-to-end workflow that we've used on our website repos. I use the specific example of mirage-decks, which builds the unikernel serving http://decks.openmirage.org. > > You might find some of these scripts useful for your own projects. The post is about a 10min read but if you're already familiar with how the new Travis scripts work, then you can skip ahead to "deployment scripts" (which is about halfway through). > > http://amirchaudhry.com/heroku-for-unikernels-pt1/ > > Best wishes, > 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 Apr 03 15:00:39 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Apr 2015 15:00: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 1Ye35D-00014o-Ji; Fri, 03 Apr 2015 15:00:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ye35D-00014c-01 for mirageos-devel@lists.xenproject.org; Fri, 03 Apr 2015 15:00:31 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id F7/45-22343-E0BAE155; Fri, 03 Apr 2015 15:00:30 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-21.messagelabs.com!1428073229!374171!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.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6746 invoked from network); 3 Apr 2015 15:00:29 -0000 Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk) (131.111.8.142) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Apr 2015 15:00:29 -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]:55929 helo=[192.168.0.33]) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Ye35B-0004ew-7b (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Fri, 03 Apr 2015 16:00:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <0D4916D8-8B16-404B-AD07-17473BE64D6E@cam.ac.uk> Date: Fri, 3 Apr 2015 16:00:30 +0100 Message-Id: <8D620BFF-88F8-48BA-A6E0-3BF7A6141B7A@cam.ac.uk> References: <0D4916D8-8B16-404B-AD07-17473BE64D6E@cam.ac.uk> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] End-to-end deployments of unikernels 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, I've posted a follow up to my earlier post, which is more about extrapolating from the tools we have now. A lot of it is speculative and considers how we might use things like Jitsu and Irmin to create demand-driven, hyper-elastic clouds. It's about a 10min read and occasionally refers to the previous post (linked down-thread). http://amirchaudhry.com/heroku-for-unikernels-pt2/ I'd be very interested to hear any feedback. Best wishes, Amir On 31 Mar 2015, at 16:11, Amir Chaudhry wrote: > Hi folks, > > I've published a post that describes the automated, end-to-end workflow that we've used on our website repos. I use the specific example of mirage-decks, which builds the unikernel serving http://decks.openmirage.org. > > You might find some of these scripts useful for your own projects. The post is about a 10min read but if you're already familiar with how the new Travis scripts work, then you can skip ahead to "deployment scripts" (which is about halfway through). > > http://amirchaudhry.com/heroku-for-unikernels-pt1/ > > Best wishes, > 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 Sat Apr 04 10:59:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 04 Apr 2015 10:59:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YeLnc-0005T3-3B; Sat, 04 Apr 2015 10:59:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YeLna-0005Sy-Nr for mirageos-devel@lists.xenproject.org; Sat, 04 Apr 2015 10:59:35 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id 0D/49-13722-614CF155; Sat, 04 Apr 2015 10:59:34 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1428145172!10124393!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18283 invoked from network); 4 Apr 2015 10:59:32 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2015 10:59:32 -0000 Received: by wgbdm7 with SMTP id dm7so128249880wgb.1 for ; Sat, 04 Apr 2015 03:59:32 -0700 (PDT) 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=4S6jERME8bOH9NXT39ZC/Bf4QNIJLBOd3fXxUW2GVW4=; b=KwwHYVmT49ZYCdvPobtT27mERNXE1E2a3pB4EPFhZymUPBPFdtocqEfqoPV1e1R/Gs veUWEnBdELAg8OZwWPus4/O3chPF+QZbgsIJEyysreV8IximFUT8UEHQuvv52ikyryVc UHQZNPKnuPHwnAPR27OTnMXTfRrRQB3yfAWTsKXVEs3TKtWEvdLUMqx2yr3FpR5uy7Aa b8W2TBZDcCHADJWoDnxbP/Ym7rYiidlkbA3+buMyX/6a6UWgtJFghz14pPICjAVKZrm8 vAsjRemjiO/jWWdLmZtvMk14lnp1xXGs6eWVLlaTjNH5eK1WFOtV7wLZv6I8DrVK5iGe mxKA== MIME-Version: 1.0 X-Received: by 10.194.190.10 with SMTP id gm10mr13066422wjc.91.1428145171983; Sat, 04 Apr 2015 03:59:31 -0700 (PDT) Received: by 10.27.14.81 with HTTP; Sat, 4 Apr 2015 03:59:31 -0700 (PDT) Date: Sat, 4 Apr 2015 11:59:31 +0100 Message-ID: From: Matthew Gray To: mirageos-devel Subject: [MirageOS-devel] Trouble building a separate module that depends on Mirage types 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="===============4631003269803126755==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4631003269803126755== Content-Type: multipart/alternative; boundary=047d7bea39f4a9f26a0512e3f5b5 --047d7bea39f4a9f26a0512e3f5b5 Content-Type: text/plain; charset=UTF-8 Hello, I've been working on this https://github.com/mattgray/horseos as a means of learning about OCaml and the Mirage project. It's a super-basic chat program that works over TCP. Like IRC with almost no features. I've got it all working so far by defining everything in unikernel.ml, and now I'm trying to split things out into modules - specifically a session module which deals with reading and writing strings to the TCP connection. This module works OK when it's also defined in unikernel.ml (see: eg https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml ) However when I pull the module out into it's own file entirely like this: ( https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml ) I get build errors from make (after doing mirage clean/configure): ocamlbuild -classic-display -use-ocamlfind -pkgs lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -tags "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" -tag-line ": -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg main.native ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence -package tcpip.stack-socket -package mirage-types.lwt -package mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo session.ml + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence -package tcpip.stack-socket -package mirage-types.lwt -package mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo session.ml File "session.ml", line 3, characters 17-35: *Error: Unbound module STACKV4* I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type which is what I really need) into scope here. It seems like mirage-types.lwt is being passed as a package into ocamlbuild, and I have tried various permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The other thing I have considered (but not tried yet) is that the session module needs to be "functorized" to work with the types from Mirage. Any pointers here would be most appreciated.... I feel like there's something simple / fundamental here that I'm completely missing! Matt --047d7bea39f4a9f26a0512e3f5b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I've been working on this https://github.com/mattgray/h= orseos=C2=A0as a means of learning about OCaml and the Mirage project. = It's a super-basic chat program that works over TCP. Like IRC with almo= st no features.

I've got it all working so far= by defining everything in unikernel.ml= , and now I'm trying to split things out into modules - specifically a = session module which deals with reading and writing strings to the TCP conn= ection. This module works OK when it's also defined in unikernel.ml (see: eg=C2=A0https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c= 8c53a6e79b/unikernel.ml )

However when I pull = the module out into it's own file entirely like this: ( https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef= 466bfa5e9fca546746871/session.ml ) I get build errors from make (after = doing mirage clean/configure):

ocamlbuild -cl= assic-display -use-ocamlfind -pkgs lwt.syntax,mirage-console.unix,mirage-ty= pes.lwt,tcpip.stack-socket -tags "syntax(camlp4o),annot,bin_annot,stri= ct_sequence,principal" -tag-line "<static*.*>: -syntax(caml= p4o)" -cflag -g -lflags -g,-linkpkg main.native
ocamlfind oc= amlc -c -g -annot -bin-annot -principal -strict-sequence -package tcpip.sta= ck-socket -package mirage-types.lwt -package mirage-console.unix -package l= wt.syntax -syntax camlp4o -o session.cmo sess= ion.ml
+ ocamlfind ocamlc -c -g -annot -bin-annot -principal = -strict-sequence -package tcpip.stack-socket -package mirage-types.lwt -pac= kage mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo= session.ml
File "session.ml", line 3, characters 17-35:
Error: Unbound module STACKV4

I= 'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type = which is what I really need) into scope here. It seems like mirage-types.lw= t is being passed as a package into ocamlbuild, and I have tried various pe= rmutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The other th= ing I have considered (but not tried yet) is that the session module needs = to be "functorized" to work with the types from Mirage.

Any pointers here would be most appreciated.... I feel like= there's something simple / fundamental here that I'm completely mi= ssing!

Matt


--047d7bea39f4a9f26a0512e3f5b5-- --===============4631003269803126755== 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 --===============4631003269803126755==-- From mirageos-devel-bounces@lists.xenproject.org Sat Apr 04 10:59:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 04 Apr 2015 10:59:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YeLnc-0005T3-3B; Sat, 04 Apr 2015 10:59:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YeLna-0005Sy-Nr for mirageos-devel@lists.xenproject.org; Sat, 04 Apr 2015 10:59:35 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id 0D/49-13722-614CF155; Sat, 04 Apr 2015 10:59:34 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1428145172!10124393!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18283 invoked from network); 4 Apr 2015 10:59:32 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2015 10:59:32 -0000 Received: by wgbdm7 with SMTP id dm7so128249880wgb.1 for ; Sat, 04 Apr 2015 03:59:32 -0700 (PDT) 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=4S6jERME8bOH9NXT39ZC/Bf4QNIJLBOd3fXxUW2GVW4=; b=KwwHYVmT49ZYCdvPobtT27mERNXE1E2a3pB4EPFhZymUPBPFdtocqEfqoPV1e1R/Gs veUWEnBdELAg8OZwWPus4/O3chPF+QZbgsIJEyysreV8IximFUT8UEHQuvv52ikyryVc UHQZNPKnuPHwnAPR27OTnMXTfRrRQB3yfAWTsKXVEs3TKtWEvdLUMqx2yr3FpR5uy7Aa b8W2TBZDcCHADJWoDnxbP/Ym7rYiidlkbA3+buMyX/6a6UWgtJFghz14pPICjAVKZrm8 vAsjRemjiO/jWWdLmZtvMk14lnp1xXGs6eWVLlaTjNH5eK1WFOtV7wLZv6I8DrVK5iGe mxKA== MIME-Version: 1.0 X-Received: by 10.194.190.10 with SMTP id gm10mr13066422wjc.91.1428145171983; Sat, 04 Apr 2015 03:59:31 -0700 (PDT) Received: by 10.27.14.81 with HTTP; Sat, 4 Apr 2015 03:59:31 -0700 (PDT) Date: Sat, 4 Apr 2015 11:59:31 +0100 Message-ID: From: Matthew Gray To: mirageos-devel Subject: [MirageOS-devel] Trouble building a separate module that depends on Mirage types 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="===============4631003269803126755==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4631003269803126755== Content-Type: multipart/alternative; boundary=047d7bea39f4a9f26a0512e3f5b5 --047d7bea39f4a9f26a0512e3f5b5 Content-Type: text/plain; charset=UTF-8 Hello, I've been working on this https://github.com/mattgray/horseos as a means of learning about OCaml and the Mirage project. It's a super-basic chat program that works over TCP. Like IRC with almost no features. I've got it all working so far by defining everything in unikernel.ml, and now I'm trying to split things out into modules - specifically a session module which deals with reading and writing strings to the TCP connection. This module works OK when it's also defined in unikernel.ml (see: eg https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml ) However when I pull the module out into it's own file entirely like this: ( https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml ) I get build errors from make (after doing mirage clean/configure): ocamlbuild -classic-display -use-ocamlfind -pkgs lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -tags "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" -tag-line ": -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg main.native ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence -package tcpip.stack-socket -package mirage-types.lwt -package mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo session.ml + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence -package tcpip.stack-socket -package mirage-types.lwt -package mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo session.ml File "session.ml", line 3, characters 17-35: *Error: Unbound module STACKV4* I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type which is what I really need) into scope here. It seems like mirage-types.lwt is being passed as a package into ocamlbuild, and I have tried various permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The other thing I have considered (but not tried yet) is that the session module needs to be "functorized" to work with the types from Mirage. Any pointers here would be most appreciated.... I feel like there's something simple / fundamental here that I'm completely missing! Matt --047d7bea39f4a9f26a0512e3f5b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I've been working on this https://github.com/mattgray/h= orseos=C2=A0as a means of learning about OCaml and the Mirage project. = It's a super-basic chat program that works over TCP. Like IRC with almo= st no features.

I've got it all working so far= by defining everything in unikernel.ml= , and now I'm trying to split things out into modules - specifically a = session module which deals with reading and writing strings to the TCP conn= ection. This module works OK when it's also defined in unikernel.ml (see: eg=C2=A0https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c= 8c53a6e79b/unikernel.ml )

However when I pull = the module out into it's own file entirely like this: ( https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef= 466bfa5e9fca546746871/session.ml ) I get build errors from make (after = doing mirage clean/configure):

ocamlbuild -cl= assic-display -use-ocamlfind -pkgs lwt.syntax,mirage-console.unix,mirage-ty= pes.lwt,tcpip.stack-socket -tags "syntax(camlp4o),annot,bin_annot,stri= ct_sequence,principal" -tag-line "<static*.*>: -syntax(caml= p4o)" -cflag -g -lflags -g,-linkpkg main.native
ocamlfind oc= amlc -c -g -annot -bin-annot -principal -strict-sequence -package tcpip.sta= ck-socket -package mirage-types.lwt -package mirage-console.unix -package l= wt.syntax -syntax camlp4o -o session.cmo sess= ion.ml
+ ocamlfind ocamlc -c -g -annot -bin-annot -principal = -strict-sequence -package tcpip.stack-socket -package mirage-types.lwt -pac= kage mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo= session.ml
File "session.ml", line 3, characters 17-35:
Error: Unbound module STACKV4

I= 'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type = which is what I really need) into scope here. It seems like mirage-types.lw= t is being passed as a package into ocamlbuild, and I have tried various pe= rmutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The other th= ing I have considered (but not tried yet) is that the session module needs = to be "functorized" to work with the types from Mirage.

Any pointers here would be most appreciated.... I feel like= there's something simple / fundamental here that I'm completely mi= ssing!

Matt


--047d7bea39f4a9f26a0512e3f5b5-- --===============4631003269803126755== 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 --===============4631003269803126755==-- From mirageos-devel-bounces@lists.xenproject.org Sat Apr 04 14:44:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 04 Apr 2015 14:44: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 1YePJT-0003MN-3A; Sat, 04 Apr 2015 14:44:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YePJR-0003MI-En for mirageos-devel@lists.xenproject.org; Sat, 04 Apr 2015 14:44:41 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id CE/CD-11242-8D8FF155; Sat, 04 Apr 2015 14:44:40 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1428158679!13799315!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 768 invoked from network); 4 Apr 2015 14:44:39 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2015 14:44:39 -0000 Received: by wizk4 with SMTP id k4so67164839wiz.1 for ; Sat, 04 Apr 2015 07:44:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jXOT8BbSMzkKDzomiNOJhke6HkxfXwgZWNh9qOhNEMU=; b=a2TYtFekQgmQZ7MvzoHkbq4YefmWL2TWdqlgopxaIqfVOKuVquMEWR6rjQ4K06Bf3G w8YGhPySN6tnlWSifmWTyXG7C7RQgGrwTC1lAQ6NJCsaIfg4P+fNsoKcRfOEY3/D2JUQ IVzGsuMpZH1+lu8M4rLR7ZWjcWYnepCyq4E/on7FcQWT0wt91djR3GluvLqU314ponWO wkWaAnazOVINian0WjefxdGXgYIM1Mk0vyfebkAi8uvVNXl5kKtH1L51Z+/vavtwt1Tb tJx8EJnKWYTtV6AT8Wrwm4V4Ofop4F2VeBNN7KISUSn6ncckg0mfEOxi2B0AvlYxojpJ Uzcg== X-Gm-Message-State: ALoCoQmwM3i14WYklNgwFCb5bvtS4hDc2qentu8PERid0meObOMDvdYL59h0ORMnRZBQ0v6GbUGp MIME-Version: 1.0 X-Received: by 10.180.88.8 with SMTP id bc8mr10486119wib.19.1428158679413; Sat, 04 Apr 2015 07:44:39 -0700 (PDT) Received: by 10.194.129.130 with HTTP; Sat, 4 Apr 2015 07:44:39 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 Apr 2015 10:44:39 -0400 Message-ID: From: Len Maxwell To: Matthew Gray Cc: mirageos-devel Subject: Re: [MirageOS-devel] Trouble building a separate module that depends on Mirage types 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 Matt, I am relatively new to all of this, but I think I can help... Start by moving the code in session.ml under a new functor (I'll call it Tcp for lack of inspiration): open Lwt module Tcp (S: V1_LWT.STACKV4) = struct type t = { flow: S.TCPV4.flow; on_close: ( string -> unit ) } (* ... *) let close session reason = session.on_close reason; S.TCPV4.close session.flow (* ... *) end Session.Tcp takes a module parameter "S" that conforms to the V1_LWT.STACKV4 signature. In unikernel.ml, we will need to instantiate a Session.Tcp module, using the STACKV4 parameter "S" fed to Unikernel.Main: open Lwt module Main (C: V1_LWT.CONSOLE) (S: V1_LWT.STACKV4) = struct module Ses = Session.Tcp(S) (* ... *) let start c s = let log message = C.log c message in let write_welcome session = Ses.write session horse_ascii in (* ... *) Neither Unikernel.Main or Session.Tcp "know" the concrete module represented by S, only that its signature matches STACKV4. When you run "mirage configure", the mirage tool uses your config.ml to choose an implementation of STACKV4 that is appropriate to your target environment, and generates main.ml to feed that module into Unikernel.Main. With these changes I was able to build and run your code in --unix. -- Len On Sat, Apr 4, 2015 at 6:59 AM, Matthew Gray wrote: > Hello, > > I've been working on this https://github.com/mattgray/horseos as a means of > learning about OCaml and the Mirage project. It's a super-basic chat program > that works over TCP. Like IRC with almost no features. > > I've got it all working so far by defining everything in unikernel.ml, and > now I'm trying to split things out into modules - specifically a session > module which deals with reading and writing strings to the TCP connection. > This module works OK when it's also defined in unikernel.ml (see: eg > https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml > ) > > However when I pull the module out into it's own file entirely like this: ( > https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml > ) I get build errors from make (after doing mirage clean/configure): > > ocamlbuild -classic-display -use-ocamlfind -pkgs > lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -tags > "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" -tag-line > ": -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg main.native > ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > -package tcpip.stack-socket -package mirage-types.lwt -package > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > session.ml > + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > -package tcpip.stack-socket -package mirage-types.lwt -package > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > session.ml > File "session.ml", line 3, characters 17-35: > Error: Unbound module STACKV4 > > I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type > which is what I really need) into scope here. It seems like mirage-types.lwt > is being passed as a package into ocamlbuild, and I have tried various > permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The other > thing I have considered (but not tried yet) is that the session module needs > to be "functorized" to work with the types from Mirage. > > Any pointers here would be most appreciated.... I feel like there's > something simple / fundamental here that I'm completely missing! > > Matt > > > > _______________________________________________ > 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 Sat Apr 04 14:44:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 04 Apr 2015 14:44: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 1YePJT-0003MN-3A; Sat, 04 Apr 2015 14:44:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YePJR-0003MI-En for mirageos-devel@lists.xenproject.org; Sat, 04 Apr 2015 14:44:41 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id CE/CD-11242-8D8FF155; Sat, 04 Apr 2015 14:44:40 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1428158679!13799315!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 768 invoked from network); 4 Apr 2015 14:44:39 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2015 14:44:39 -0000 Received: by wizk4 with SMTP id k4so67164839wiz.1 for ; Sat, 04 Apr 2015 07:44:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jXOT8BbSMzkKDzomiNOJhke6HkxfXwgZWNh9qOhNEMU=; b=a2TYtFekQgmQZ7MvzoHkbq4YefmWL2TWdqlgopxaIqfVOKuVquMEWR6rjQ4K06Bf3G w8YGhPySN6tnlWSifmWTyXG7C7RQgGrwTC1lAQ6NJCsaIfg4P+fNsoKcRfOEY3/D2JUQ IVzGsuMpZH1+lu8M4rLR7ZWjcWYnepCyq4E/on7FcQWT0wt91djR3GluvLqU314ponWO wkWaAnazOVINian0WjefxdGXgYIM1Mk0vyfebkAi8uvVNXl5kKtH1L51Z+/vavtwt1Tb tJx8EJnKWYTtV6AT8Wrwm4V4Ofop4F2VeBNN7KISUSn6ncckg0mfEOxi2B0AvlYxojpJ Uzcg== X-Gm-Message-State: ALoCoQmwM3i14WYklNgwFCb5bvtS4hDc2qentu8PERid0meObOMDvdYL59h0ORMnRZBQ0v6GbUGp MIME-Version: 1.0 X-Received: by 10.180.88.8 with SMTP id bc8mr10486119wib.19.1428158679413; Sat, 04 Apr 2015 07:44:39 -0700 (PDT) Received: by 10.194.129.130 with HTTP; Sat, 4 Apr 2015 07:44:39 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 Apr 2015 10:44:39 -0400 Message-ID: From: Len Maxwell To: Matthew Gray Cc: mirageos-devel Subject: Re: [MirageOS-devel] Trouble building a separate module that depends on Mirage types 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 Matt, I am relatively new to all of this, but I think I can help... Start by moving the code in session.ml under a new functor (I'll call it Tcp for lack of inspiration): open Lwt module Tcp (S: V1_LWT.STACKV4) = struct type t = { flow: S.TCPV4.flow; on_close: ( string -> unit ) } (* ... *) let close session reason = session.on_close reason; S.TCPV4.close session.flow (* ... *) end Session.Tcp takes a module parameter "S" that conforms to the V1_LWT.STACKV4 signature. In unikernel.ml, we will need to instantiate a Session.Tcp module, using the STACKV4 parameter "S" fed to Unikernel.Main: open Lwt module Main (C: V1_LWT.CONSOLE) (S: V1_LWT.STACKV4) = struct module Ses = Session.Tcp(S) (* ... *) let start c s = let log message = C.log c message in let write_welcome session = Ses.write session horse_ascii in (* ... *) Neither Unikernel.Main or Session.Tcp "know" the concrete module represented by S, only that its signature matches STACKV4. When you run "mirage configure", the mirage tool uses your config.ml to choose an implementation of STACKV4 that is appropriate to your target environment, and generates main.ml to feed that module into Unikernel.Main. With these changes I was able to build and run your code in --unix. -- Len On Sat, Apr 4, 2015 at 6:59 AM, Matthew Gray wrote: > Hello, > > I've been working on this https://github.com/mattgray/horseos as a means of > learning about OCaml and the Mirage project. It's a super-basic chat program > that works over TCP. Like IRC with almost no features. > > I've got it all working so far by defining everything in unikernel.ml, and > now I'm trying to split things out into modules - specifically a session > module which deals with reading and writing strings to the TCP connection. > This module works OK when it's also defined in unikernel.ml (see: eg > https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml > ) > > However when I pull the module out into it's own file entirely like this: ( > https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml > ) I get build errors from make (after doing mirage clean/configure): > > ocamlbuild -classic-display -use-ocamlfind -pkgs > lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -tags > "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" -tag-line > ": -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg main.native > ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > -package tcpip.stack-socket -package mirage-types.lwt -package > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > session.ml > + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > -package tcpip.stack-socket -package mirage-types.lwt -package > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > session.ml > File "session.ml", line 3, characters 17-35: > Error: Unbound module STACKV4 > > I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type > which is what I really need) into scope here. It seems like mirage-types.lwt > is being passed as a package into ocamlbuild, and I have tried various > permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The other > thing I have considered (but not tried yet) is that the session module needs > to be "functorized" to work with the types from Mirage. > > Any pointers here would be most appreciated.... I feel like there's > something simple / fundamental here that I'm completely missing! > > Matt > > > > _______________________________________________ > 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 Mon Apr 06 10:33:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Apr 2015 10:33: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 1Yf4LX-0001mH-E4; Mon, 06 Apr 2015 10:33:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yf4LW-0001mC-65 for mirageos-devel@lists.xenproject.org; Mon, 06 Apr 2015 10:33:34 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 94/BB-02119-DF062255; Mon, 06 Apr 2015 10:33:33 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1428316411!13947006!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17813 invoked from network); 6 Apr 2015 10:33:31 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2015 10:33:31 -0000 Received: by wiun10 with SMTP id n10so30503027wiu.1 for ; Mon, 06 Apr 2015 03:33:31 -0700 (PDT) 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=ooS9dFtridbuO2N/uOTCtUS8TiMncVy1keMbdn5HCPU=; b=dNbWhnN8Yhj+sB3kAft3zYIYTSJdhuF0ywxBcgbAcQeypJoRAimY+mXYBHBSckUccC iYEX994gDGxJnwXqkramLf3FGFUZA/AwRGLPuMQPRra6zsiS5xOkQYYSHStiCukq2fv4 ng7lVxTRc8XsuU8wimNEcgX7i+E6467yGzC/BopnTdIGHupD6mwqL7WbaBmrpP8hO+k+ dpcY2FhhwxOTlii2KMjdx2msa9gMcgiOi6fxcMVIyY5xZpDCbNfU/nhx9ZoBQwRMO57I zGm7V/y1KaU7232mRkoGOxWAaWPORVupbailZzaZMUKdafOV32ODSAqKKtx7ZRfSm4Gx 7Ttw== MIME-Version: 1.0 X-Received: by 10.194.190.10 with SMTP id gm10mr29800248wjc.91.1428316411456; Mon, 06 Apr 2015 03:33:31 -0700 (PDT) Received: by 10.27.14.14 with HTTP; Mon, 6 Apr 2015 03:33:31 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Apr 2015 11:33:31 +0100 Message-ID: From: Matthew Gray To: Len Maxwell Cc: mirageos-devel Subject: Re: [MirageOS-devel] Trouble building a separate module that depends on Mirage types 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="===============5792766022294838156==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5792766022294838156== Content-Type: multipart/alternative; boundary=047d7bea39f454f14a05130bd43c --047d7bea39f454f14a05130bd43c Content-Type: text/plain; charset=UTF-8 Great... thank you - that did it. Starting to understand how all these things plug together now... the functor allows the Session module to be told which implementation of STACKV4 to use. On Sat, Apr 4, 2015 at 3:44 PM, Len Maxwell wrote: > Hi Matt, > > I am relatively new to all of this, but I think I can help... > > Start by moving the code in session.ml under a new functor (I'll call > it Tcp for lack of inspiration): > > open Lwt > > module Tcp (S: V1_LWT.STACKV4) = struct > > type t = { flow: S.TCPV4.flow; on_close: ( string -> unit ) } > > (* ... *) > > let close session reason = > session.on_close reason; > S.TCPV4.close session.flow > > (* ... *) > > end > > Session.Tcp takes a module parameter "S" that conforms to the > V1_LWT.STACKV4 signature. > > In unikernel.ml, we will need to instantiate a Session.Tcp module, > using the STACKV4 parameter "S" fed to Unikernel.Main: > > open Lwt > > module Main (C: V1_LWT.CONSOLE) (S: V1_LWT.STACKV4) = struct > > module Ses = Session.Tcp(S) > > (* ... *) > > let start c s = > let log message = C.log c message in > > let write_welcome session = Ses.write session horse_ascii in > > (* ... *) > > Neither Unikernel.Main or Session.Tcp "know" the concrete module > represented by S, only that its signature matches STACKV4. When you > run "mirage configure", the mirage tool uses your config.ml to choose > an implementation of STACKV4 that is appropriate to your target > environment, and generates main.ml to feed that module into > Unikernel.Main. > > With these changes I was able to build and run your code in --unix. > > > -- > Len > > On Sat, Apr 4, 2015 at 6:59 AM, Matthew Gray > wrote: > > Hello, > > > > I've been working on this https://github.com/mattgray/horseos as a > means of > > learning about OCaml and the Mirage project. It's a super-basic chat > program > > that works over TCP. Like IRC with almost no features. > > > > I've got it all working so far by defining everything in unikernel.ml, > and > > now I'm trying to split things out into modules - specifically a session > > module which deals with reading and writing strings to the TCP > connection. > > This module works OK when it's also defined in unikernel.ml (see: eg > > > https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml > > ) > > > > However when I pull the module out into it's own file entirely like > this: ( > > > https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml > > ) I get build errors from make (after doing mirage clean/configure): > > > > ocamlbuild -classic-display -use-ocamlfind -pkgs > > lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -tags > > "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" -tag-line > > ": -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg main.native > > ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > > -package tcpip.stack-socket -package mirage-types.lwt -package > > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > > session.ml > > + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > > -package tcpip.stack-socket -package mirage-types.lwt -package > > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > > session.ml > > File "session.ml", line 3, characters 17-35: > > Error: Unbound module STACKV4 > > > > I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type > > which is what I really need) into scope here. It seems like > mirage-types.lwt > > is being passed as a package into ocamlbuild, and I have tried various > > permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The > other > > thing I have considered (but not tried yet) is that the session module > needs > > to be "functorized" to work with the types from Mirage. > > > > Any pointers here would be most appreciated.... I feel like there's > > something simple / fundamental here that I'm completely missing! > > > > Matt > > > > > > > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > --047d7bea39f454f14a05130bd43c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Great... thank you - that did it. Starting to understand h= ow all these things plug together now... the functor allows the Session mod= ule to be told which implementation of STACKV4 to use.

On Sat, Apr 4, 2015 at 3:44 PM, = Len Maxwell <len@lnmx.org> wrote:
Hi Matt,

I am relatively new to all of this, but I think I can help...

Start by moving the code in session.ml under a new functor (I'll call
it Tcp for lack of inspiration):

=C2=A0 =C2=A0 open Lwt

=C2=A0 =C2=A0 module Tcp (S: V1_LWT.STACKV4) =3D struct

=C2=A0 =C2=A0 =C2=A0 type t =3D { flow: S.TCPV4.flow; on_close: ( string -&= gt; unit ) }

=C2=A0 =C2=A0 =C2=A0 (* ... *)

=C2=A0 =C2=A0 =C2=A0 let close session reason =3D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 session.on_close reason;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 S.TCPV4.close session.flow

=C2=A0 =C2=A0 =C2=A0 (* ... *)

=C2=A0 =C2=A0 end

Session.Tcp takes a module parameter "S" that conforms to the
V1_LWT.STACKV4 signature.

In unikernel.ml, we w= ill need to instantiate a Session.Tcp module,
using the STACKV4 parameter "S" fed to Unikernel.Main:

=C2=A0 =C2=A0 open Lwt

=C2=A0 =C2=A0 module Main (C: V1_LWT.CONSOLE) (S: V1_LWT.STACKV4) =3D struc= t

=C2=A0 =C2=A0 =C2=A0 module Ses =3D Session.Tcp(S)

=C2=A0 =C2=A0 =C2=A0 (* ... *)

=C2=A0 =C2=A0 =C2=A0 let start c s =3D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 let log message =3D C.log c message in

=C2=A0 =C2=A0 =C2=A0 =C2=A0 let write_welcome session =3D Ses.write session= horse_ascii in

=C2=A0 =C2=A0 =C2=A0 (* ... *)

Neither Unikernel.Main or Session.Tcp "know" the concrete module<= br> represented by S, only that its signature matches STACKV4.=C2=A0 When you run "mirage configure", the mirage tool uses your config.ml to choose
an implementation of STACKV4 that is appropriate to your target
environment, and generates mai= n.ml to feed that module into
Unikernel.Main.

With these changes I was able to build and run your code in --unix.


--
Len

On Sat, Apr 4, 2015 at 6:59 AM, Matthew Gray
<matthew.thomas.gray@gm= ail.com> wrote:
> Hello,
>
> I've been working on this https://github.com/mattgray/horseos as a mean= s of
> learning about OCaml and the Mirage project. It's a super-basic ch= at program
> that works over TCP. Like IRC with almost no features.
>
> I've got it all working so far by defining everything in unikernel.ml, and
> now I'm trying to split things out into modules - specifically a s= ession
> module which deals with reading and writing strings to the TCP connect= ion.
> This module works OK when it's also defined in unikernel.ml (see: eg
> https://github.com/m= attgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml<= /a>
> )
>
> However when I pull the module out into it's own file entirely lik= e this: (
> https://github.com/mat= tgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml<= br> > ) I get build errors from make (after doing mirage clean/configure): >
> ocamlbuild -classic-display -use-ocamlfind -pkgs
> lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -ta= gs
> "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" = -tag-line
> "<static*.*>: -syntax(camlp4o)" -cflag -g -lflags -g,-= linkpkg main.native
> ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > -package tcpip.stack-socket -package mirage-types.lwt -package
> mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo=
> session.ml
> + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence=
> -package tcpip.stack-socket -package mirage-types.lwt -package
> mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo=
> session.ml
> File "session.ml<= /a>", line 3, characters 17-35:
> Error: Unbound module STACKV4
>
> I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow= type
> which is what I really need) into scope here. It seems like mirage-typ= es.lwt
> is being passed as a package into ocamlbuild, and I have tried various=
> permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The o= ther
> thing I have considered (but not tried yet) is that the session module= needs
> to be "functorized" to work with the types from Mirage.
>
> Any pointers here would be most appreciated.... I feel like there'= s
> something simple / fundamental here that I'm completely missing! >
> Matt
>
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@= lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel
>

--047d7bea39f454f14a05130bd43c-- --===============5792766022294838156== 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 --===============5792766022294838156==-- From mirageos-devel-bounces@lists.xenproject.org Mon Apr 06 10:33:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Apr 2015 10:33: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 1Yf4LX-0001mH-E4; Mon, 06 Apr 2015 10:33:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yf4LW-0001mC-65 for mirageos-devel@lists.xenproject.org; Mon, 06 Apr 2015 10:33:34 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 94/BB-02119-DF062255; Mon, 06 Apr 2015 10:33:33 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1428316411!13947006!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17813 invoked from network); 6 Apr 2015 10:33:31 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2015 10:33:31 -0000 Received: by wiun10 with SMTP id n10so30503027wiu.1 for ; Mon, 06 Apr 2015 03:33:31 -0700 (PDT) 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=ooS9dFtridbuO2N/uOTCtUS8TiMncVy1keMbdn5HCPU=; b=dNbWhnN8Yhj+sB3kAft3zYIYTSJdhuF0ywxBcgbAcQeypJoRAimY+mXYBHBSckUccC iYEX994gDGxJnwXqkramLf3FGFUZA/AwRGLPuMQPRra6zsiS5xOkQYYSHStiCukq2fv4 ng7lVxTRc8XsuU8wimNEcgX7i+E6467yGzC/BopnTdIGHupD6mwqL7WbaBmrpP8hO+k+ dpcY2FhhwxOTlii2KMjdx2msa9gMcgiOi6fxcMVIyY5xZpDCbNfU/nhx9ZoBQwRMO57I zGm7V/y1KaU7232mRkoGOxWAaWPORVupbailZzaZMUKdafOV32ODSAqKKtx7ZRfSm4Gx 7Ttw== MIME-Version: 1.0 X-Received: by 10.194.190.10 with SMTP id gm10mr29800248wjc.91.1428316411456; Mon, 06 Apr 2015 03:33:31 -0700 (PDT) Received: by 10.27.14.14 with HTTP; Mon, 6 Apr 2015 03:33:31 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Apr 2015 11:33:31 +0100 Message-ID: From: Matthew Gray To: Len Maxwell Cc: mirageos-devel Subject: Re: [MirageOS-devel] Trouble building a separate module that depends on Mirage types 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="===============5792766022294838156==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5792766022294838156== Content-Type: multipart/alternative; boundary=047d7bea39f454f14a05130bd43c --047d7bea39f454f14a05130bd43c Content-Type: text/plain; charset=UTF-8 Great... thank you - that did it. Starting to understand how all these things plug together now... the functor allows the Session module to be told which implementation of STACKV4 to use. On Sat, Apr 4, 2015 at 3:44 PM, Len Maxwell wrote: > Hi Matt, > > I am relatively new to all of this, but I think I can help... > > Start by moving the code in session.ml under a new functor (I'll call > it Tcp for lack of inspiration): > > open Lwt > > module Tcp (S: V1_LWT.STACKV4) = struct > > type t = { flow: S.TCPV4.flow; on_close: ( string -> unit ) } > > (* ... *) > > let close session reason = > session.on_close reason; > S.TCPV4.close session.flow > > (* ... *) > > end > > Session.Tcp takes a module parameter "S" that conforms to the > V1_LWT.STACKV4 signature. > > In unikernel.ml, we will need to instantiate a Session.Tcp module, > using the STACKV4 parameter "S" fed to Unikernel.Main: > > open Lwt > > module Main (C: V1_LWT.CONSOLE) (S: V1_LWT.STACKV4) = struct > > module Ses = Session.Tcp(S) > > (* ... *) > > let start c s = > let log message = C.log c message in > > let write_welcome session = Ses.write session horse_ascii in > > (* ... *) > > Neither Unikernel.Main or Session.Tcp "know" the concrete module > represented by S, only that its signature matches STACKV4. When you > run "mirage configure", the mirage tool uses your config.ml to choose > an implementation of STACKV4 that is appropriate to your target > environment, and generates main.ml to feed that module into > Unikernel.Main. > > With these changes I was able to build and run your code in --unix. > > > -- > Len > > On Sat, Apr 4, 2015 at 6:59 AM, Matthew Gray > wrote: > > Hello, > > > > I've been working on this https://github.com/mattgray/horseos as a > means of > > learning about OCaml and the Mirage project. It's a super-basic chat > program > > that works over TCP. Like IRC with almost no features. > > > > I've got it all working so far by defining everything in unikernel.ml, > and > > now I'm trying to split things out into modules - specifically a session > > module which deals with reading and writing strings to the TCP > connection. > > This module works OK when it's also defined in unikernel.ml (see: eg > > > https://github.com/mattgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml > > ) > > > > However when I pull the module out into it's own file entirely like > this: ( > > > https://github.com/mattgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml > > ) I get build errors from make (after doing mirage clean/configure): > > > > ocamlbuild -classic-display -use-ocamlfind -pkgs > > lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -tags > > "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" -tag-line > > ": -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg main.native > > ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > > -package tcpip.stack-socket -package mirage-types.lwt -package > > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > > session.ml > > + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > > -package tcpip.stack-socket -package mirage-types.lwt -package > > mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo > > session.ml > > File "session.ml", line 3, characters 17-35: > > Error: Unbound module STACKV4 > > > > I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow type > > which is what I really need) into scope here. It seems like > mirage-types.lwt > > is being passed as a package into ocamlbuild, and I have tried various > > permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The > other > > thing I have considered (but not tried yet) is that the session module > needs > > to be "functorized" to work with the types from Mirage. > > > > Any pointers here would be most appreciated.... I feel like there's > > something simple / fundamental here that I'm completely missing! > > > > Matt > > > > > > > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > --047d7bea39f454f14a05130bd43c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Great... thank you - that did it. Starting to understand h= ow all these things plug together now... the functor allows the Session mod= ule to be told which implementation of STACKV4 to use.

On Sat, Apr 4, 2015 at 3:44 PM, = Len Maxwell <len@lnmx.org> wrote:
Hi Matt,

I am relatively new to all of this, but I think I can help...

Start by moving the code in session.ml under a new functor (I'll call
it Tcp for lack of inspiration):

=C2=A0 =C2=A0 open Lwt

=C2=A0 =C2=A0 module Tcp (S: V1_LWT.STACKV4) =3D struct

=C2=A0 =C2=A0 =C2=A0 type t =3D { flow: S.TCPV4.flow; on_close: ( string -&= gt; unit ) }

=C2=A0 =C2=A0 =C2=A0 (* ... *)

=C2=A0 =C2=A0 =C2=A0 let close session reason =3D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 session.on_close reason;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 S.TCPV4.close session.flow

=C2=A0 =C2=A0 =C2=A0 (* ... *)

=C2=A0 =C2=A0 end

Session.Tcp takes a module parameter "S" that conforms to the
V1_LWT.STACKV4 signature.

In unikernel.ml, we w= ill need to instantiate a Session.Tcp module,
using the STACKV4 parameter "S" fed to Unikernel.Main:

=C2=A0 =C2=A0 open Lwt

=C2=A0 =C2=A0 module Main (C: V1_LWT.CONSOLE) (S: V1_LWT.STACKV4) =3D struc= t

=C2=A0 =C2=A0 =C2=A0 module Ses =3D Session.Tcp(S)

=C2=A0 =C2=A0 =C2=A0 (* ... *)

=C2=A0 =C2=A0 =C2=A0 let start c s =3D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 let log message =3D C.log c message in

=C2=A0 =C2=A0 =C2=A0 =C2=A0 let write_welcome session =3D Ses.write session= horse_ascii in

=C2=A0 =C2=A0 =C2=A0 (* ... *)

Neither Unikernel.Main or Session.Tcp "know" the concrete module<= br> represented by S, only that its signature matches STACKV4.=C2=A0 When you run "mirage configure", the mirage tool uses your config.ml to choose
an implementation of STACKV4 that is appropriate to your target
environment, and generates mai= n.ml to feed that module into
Unikernel.Main.

With these changes I was able to build and run your code in --unix.


--
Len

On Sat, Apr 4, 2015 at 6:59 AM, Matthew Gray
<matthew.thomas.gray@gm= ail.com> wrote:
> Hello,
>
> I've been working on this https://github.com/mattgray/horseos as a mean= s of
> learning about OCaml and the Mirage project. It's a super-basic ch= at program
> that works over TCP. Like IRC with almost no features.
>
> I've got it all working so far by defining everything in unikernel.ml, and
> now I'm trying to split things out into modules - specifically a s= ession
> module which deals with reading and writing strings to the TCP connect= ion.
> This module works OK when it's also defined in unikernel.ml (see: eg
> https://github.com/m= attgray/horseos/blob/2563d75b59d95f4a69937cee690f6c8c53a6e79b/unikernel.ml<= /a>
> )
>
> However when I pull the module out into it's own file entirely lik= e this: (
> https://github.com/mat= tgray/horseos/blob/4e7e419ee06e8e245ef466bfa5e9fca546746871/session.ml<= br> > ) I get build errors from make (after doing mirage clean/configure): >
> ocamlbuild -classic-display -use-ocamlfind -pkgs
> lwt.syntax,mirage-console.unix,mirage-types.lwt,tcpip.stack-socket -ta= gs
> "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" = -tag-line
> "<static*.*>: -syntax(camlp4o)" -cflag -g -lflags -g,-= linkpkg main.native
> ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence > -package tcpip.stack-socket -package mirage-types.lwt -package
> mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo=
> session.ml
> + ocamlfind ocamlc -c -g -annot -bin-annot -principal -strict-sequence=
> -package tcpip.stack-socket -package mirage-types.lwt -package
> mirage-console.unix -package lwt.syntax -syntax camlp4o -o session.cmo=
> session.ml
> File "session.ml<= /a>", line 3, characters 17-35:
> Error: Unbound module STACKV4
>
> I'm not sure how to make the STACKV4 (or ultimately the TCPV4.flow= type
> which is what I really need) into scope here. It seems like mirage-typ= es.lwt
> is being passed as a package into ocamlbuild, and I have tried various=
> permutations on open-ing V1, V1_LWT, V1_LWT.STACKV4 to no avail. The o= ther
> thing I have considered (but not tried yet) is that the session module= needs
> to be "functorized" to work with the types from Mirage.
>
> Any pointers here would be most appreciated.... I feel like there'= s
> something simple / fundamental here that I'm completely missing! >
> Matt
>
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@= lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel
>

--047d7bea39f454f14a05130bd43c-- --===============5792766022294838156== 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 --===============5792766022294838156==-- From mirageos-devel-bounces@lists.xenproject.org Tue Apr 07 09:51:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 09:51: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 1YfQAV-0004pK-5X; Tue, 07 Apr 2015 09:51:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfQAT-0004pF-FU for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 09:51:37 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 80/CB-20070-8A8A3255; Tue, 07 Apr 2015 09:51:36 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1428400292!14105723!1 X-Originating-IP: [98.138.121.62] X-SpamReason: No, hits=0.9 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10163 invoked from network); 7 Apr 2015 09:51:33 -0000 Received: from nm42-vm6.bullet.mail.ne1.yahoo.com (HELO nm42-vm6.bullet.mail.ne1.yahoo.com) (98.138.121.62) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 09:51:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1428400292; bh=ZGtjz9L4gY5jfyMe/fJFdIYrX9u9ph9LTz9eoIrAPhI=; h=Date:From:Reply-To:To:Subject:From:Subject; b=b6LtXM1RXXhl1j1+JCvbVXi/k7k2XpwzMmMqWEgoReicAB7vhXQT2ocm+ffQjs69K7utrsI689thYaHi99u8ZG1FVZYTY0PSmpWs8kp3C3faIde5KUtswY86j5/qKn7mRW0L2BbqFWvzLKilPx4A6xfnfdDnWWOMPyVBJPdAUuq/o8UK3aa0pHsAiQ7Fhvoe+aDOxkiQnhB+9r6FX+/vjC6av+snuTgnM98/95BvbkBGt3PBFvhSojjvVULuS25dfjivQD134dcfDNyk7ZvGM3sx+/QTPXuK3XfC/hOkS3w4W4Fur2HG1q2dKTLeE2X4UJPWN1s9q02YITTL9GsFRQ== Received: from [127.0.0.1] by nm42.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 09:51:32 -0000 Received: from [98.138.100.103] by nm42.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 09:48:32 -0000 Received: from [98.139.215.140] by tm102.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 09:48:31 -0000 Received: from [98.139.212.212] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 09:48:31 -0000 Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 09:48:31 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 645101.70767.bm@omp1021.mail.bf1.yahoo.com X-YMail-OSG: YFoKa2sVM1lNSSSKUiLzyN0EKiePDVCOzAaKdObMroeXB3qKhpRHXIqV8c22TZf amLUvswvNoTHzKWjbXqWKKcsCAUVUpmKZ6PYa5rSfLJvmhiVQxSDz79_MKvY9ksronB3MIWlVosa ssLiHS7f3RZk8oVYsKGwQWdfS.9BeLeov.zTWNhUnRFuyJb_Fy3IvqP70frJpf4ts0eB.c55MQkn RF1xts02EV92QJSDHcCEFsGoXUyS7uCiOQWHqIwX9LRe69wi94i8sK96vVtej9PdxmQ.2Yz1LhSY 1DoCOqoJqMKH_F.onou6CjqeFoEnI9eBLRAqQyVkv0kOa22ijtqLtyjgtbZpqzRB9SB0cNwvpGUh ULBO52.wiMt.56Eiy6fmc0gF5tsnF9egV19OvadLvQ5gtBQJ9KtvAXTzN1BPNWWxdauwGbDACYDa tPaPmxSKWDf9FkZO2LjzHc1.tujrZV0LcB_3h0fyWOqCK4vAP4V2XVcb2gV9lu6YUz0G5ZA-- Received: by 76.13.27.35; Tue, 07 Apr 2015 09:48:31 +0000 Date: Tue, 7 Apr 2015 09:48:00 +0000 (UTC) From: Ania Skorupa To: Mirageos-devel Message-ID: <945649343.1107141.1428400080274.JavaMail.yahoo@mail.yahoo.com> MIME-Version: 1.0 Content-Length: 10928 Subject: [MirageOS-devel] Signature mismatch in tcpip 2.2.3 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1558379887057102191==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1558379887057102191== Content-Type: multipart/alternative; boundary="----=_Part_1107140_1407820520.1428400080269" Content-Length: 10384 ------=_Part_1107140_1407820520.1428400080269 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have pinned tcpip 2.2.3 to opam and receive the following error when buil= ding a network application (e.g. network in mirage-skeleton): Error: Signature mismatch: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Modules do not match: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functor (C : V1.CLOCK) (T = : V1_LWT.TIME) -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sig =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe buffer =3D Cstruct.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ethif =3D Stackv41_E.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ipaddr =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe prefix =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe error =3D [ `Unimplemented | `Unknown of string ] =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe 'a io =3D 'a Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe t =3D Ipv4.Make(Stackv41_E)(C)(T).t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l disconnect : t -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe callback =3D src:ipaddr -> dst:ipaddr -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 tcp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 udp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 default:(proto:int -> callback) -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l allocate_frame : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 dst:ipaddr -> proto:[ `ICMP | `TCP | `UDP ] -> buffer * int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l write : t -> buffer -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l writev : t -> buffer -> buffer list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l checksum : buffer -> buffer list -> int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_source : t -> dst:ipaddr -> ipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip : t -> ipaddr -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_netmask : t -> prefix -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_netmasks : t -> prefix list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_gateways : t -> ipaddr list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_gateways : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe uipaddr =3D Ipaddr.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l to_uipaddr : ipaddr -> uipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l of_uipaddr : uipaddr -> ipaddr option =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input_arpv4 : t -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l connect : ethif -> [> `Error of error | `Ok of t ] Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 end =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is not included in =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 V1_LWT.IP Any hotfix for that? ------=_Part_1107140_1407820520.1428400080269 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I hav= e pinned tcpip 2.2.3 to opam and receive the following error when building = a network application (e.g. network in mirage-skeleton):

Error: Signature mismatch:
       Modules do not match:
         functo= r (C : V1.CLOCK) (T : V1_LWT.TIME) ->
 &nb= sp;         sig
           &nb= sp; type buffer =3D Cstruct.t
   &n= bsp;         type ethif =3D Stackv4= 1_E.t
       &n= bsp;     type ipaddr =3D Ipaddr.V4.t
           &n= bsp; type prefix =3D Ipaddr.V4.t
   = ;          type error =3D [ `U= nimplemented | `Unknown of string ]
  &n= bsp;          type 'a io =3D '= a Lwt.t
       =       type t =3D Ipv4.Make(Stackv41_E)(C)(T).t
         = ;    val disconnect : t -> unit io
            = type callback =3D src:ipaddr -> dst:ipaddr -> buffer -> unit io        &nb= sp;    val input :
  &nbs= p;            t ->= ;
        =        tcp:callback ->
           &nb= sp;   udp:callback ->
  &nb= sp;            defau= lt:(proto:int -> callback) -> buffer -> unit io
           &n= bsp; val allocate_frame :
    =            t ->
         &n= bsp;     dst:ipaddr -> proto:[ `ICMP | `TCP | `UDP ]= -> buffer * int
     =         val write : t -> buffer ->= buffer -> unit io
    &nbs= p;        val writev : t -> buffer -&= gt; buffer list -> unit io
   &n= bsp;         val checksum : buffer = -> buffer list -> int
   &nbs= p;         val get_source : t ->= dst:ipaddr -> ipaddr
    &= nbsp;        val set_ip : t -> ipaddr= -> unit io
      = ;       val get_ip : t -> ipaddr list
         =     val set_ip_netmask : t -> prefix -> unit io
         &n= bsp;   val get_ip_netmasks : t -> prefix list
           =   val set_ip_gateways : t -> ipaddr list -> unit io
          &n= bsp;  val get_ip_gateways : t -> ipaddr list
            = type uipaddr =3D Ipaddr.t
    = ;         val to_uipaddr : ipaddr -= > uipaddr
      &= nbsp;      val of_uipaddr : uipaddr -> ipaddr o= ption
       &n= bsp;     val input_arpv4 : t -> buffer -> unit io=
        &= nbsp;    val connect : ethif -> [> `Error of error | `= Ok of t ] Lwt.t
     &nbs= p;     end
   &= nbsp;   is not included in
  &= nbsp;      V1_LWT.IP

Any hotfix for that?
------=_Part_1107140_1407820520.1428400080269-- --===============1558379887057102191== 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 --===============1558379887057102191==-- From mirageos-devel-bounces@lists.xenproject.org Tue Apr 07 09:51:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 09:51: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 1YfQAV-0004pK-5X; Tue, 07 Apr 2015 09:51:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfQAT-0004pF-FU for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 09:51:37 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 80/CB-20070-8A8A3255; Tue, 07 Apr 2015 09:51:36 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1428400292!14105723!1 X-Originating-IP: [98.138.121.62] X-SpamReason: No, hits=0.9 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10163 invoked from network); 7 Apr 2015 09:51:33 -0000 Received: from nm42-vm6.bullet.mail.ne1.yahoo.com (HELO nm42-vm6.bullet.mail.ne1.yahoo.com) (98.138.121.62) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 09:51:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1428400292; bh=ZGtjz9L4gY5jfyMe/fJFdIYrX9u9ph9LTz9eoIrAPhI=; h=Date:From:Reply-To:To:Subject:From:Subject; b=b6LtXM1RXXhl1j1+JCvbVXi/k7k2XpwzMmMqWEgoReicAB7vhXQT2ocm+ffQjs69K7utrsI689thYaHi99u8ZG1FVZYTY0PSmpWs8kp3C3faIde5KUtswY86j5/qKn7mRW0L2BbqFWvzLKilPx4A6xfnfdDnWWOMPyVBJPdAUuq/o8UK3aa0pHsAiQ7Fhvoe+aDOxkiQnhB+9r6FX+/vjC6av+snuTgnM98/95BvbkBGt3PBFvhSojjvVULuS25dfjivQD134dcfDNyk7ZvGM3sx+/QTPXuK3XfC/hOkS3w4W4Fur2HG1q2dKTLeE2X4UJPWN1s9q02YITTL9GsFRQ== Received: from [127.0.0.1] by nm42.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 09:51:32 -0000 Received: from [98.138.100.103] by nm42.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 09:48:32 -0000 Received: from [98.139.215.140] by tm102.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 09:48:31 -0000 Received: from [98.139.212.212] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 09:48:31 -0000 Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 09:48:31 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 645101.70767.bm@omp1021.mail.bf1.yahoo.com X-YMail-OSG: YFoKa2sVM1lNSSSKUiLzyN0EKiePDVCOzAaKdObMroeXB3qKhpRHXIqV8c22TZf amLUvswvNoTHzKWjbXqWKKcsCAUVUpmKZ6PYa5rSfLJvmhiVQxSDz79_MKvY9ksronB3MIWlVosa ssLiHS7f3RZk8oVYsKGwQWdfS.9BeLeov.zTWNhUnRFuyJb_Fy3IvqP70frJpf4ts0eB.c55MQkn RF1xts02EV92QJSDHcCEFsGoXUyS7uCiOQWHqIwX9LRe69wi94i8sK96vVtej9PdxmQ.2Yz1LhSY 1DoCOqoJqMKH_F.onou6CjqeFoEnI9eBLRAqQyVkv0kOa22ijtqLtyjgtbZpqzRB9SB0cNwvpGUh ULBO52.wiMt.56Eiy6fmc0gF5tsnF9egV19OvadLvQ5gtBQJ9KtvAXTzN1BPNWWxdauwGbDACYDa tPaPmxSKWDf9FkZO2LjzHc1.tujrZV0LcB_3h0fyWOqCK4vAP4V2XVcb2gV9lu6YUz0G5ZA-- Received: by 76.13.27.35; Tue, 07 Apr 2015 09:48:31 +0000 Date: Tue, 7 Apr 2015 09:48:00 +0000 (UTC) From: Ania Skorupa To: Mirageos-devel Message-ID: <945649343.1107141.1428400080274.JavaMail.yahoo@mail.yahoo.com> MIME-Version: 1.0 Content-Length: 10928 Subject: [MirageOS-devel] Signature mismatch in tcpip 2.2.3 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1558379887057102191==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1558379887057102191== Content-Type: multipart/alternative; boundary="----=_Part_1107140_1407820520.1428400080269" Content-Length: 10384 ------=_Part_1107140_1407820520.1428400080269 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have pinned tcpip 2.2.3 to opam and receive the following error when buil= ding a network application (e.g. network in mirage-skeleton): Error: Signature mismatch: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Modules do not match: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functor (C : V1.CLOCK) (T = : V1_LWT.TIME) -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sig =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe buffer =3D Cstruct.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ethif =3D Stackv41_E.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ipaddr =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe prefix =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe error =3D [ `Unimplemented | `Unknown of string ] =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe 'a io =3D 'a Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe t =3D Ipv4.Make(Stackv41_E)(C)(T).t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l disconnect : t -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe callback =3D src:ipaddr -> dst:ipaddr -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 tcp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 udp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 default:(proto:int -> callback) -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l allocate_frame : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 dst:ipaddr -> proto:[ `ICMP | `TCP | `UDP ] -> buffer * int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l write : t -> buffer -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l writev : t -> buffer -> buffer list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l checksum : buffer -> buffer list -> int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_source : t -> dst:ipaddr -> ipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip : t -> ipaddr -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_netmask : t -> prefix -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_netmasks : t -> prefix list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_gateways : t -> ipaddr list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_gateways : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe uipaddr =3D Ipaddr.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l to_uipaddr : ipaddr -> uipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l of_uipaddr : uipaddr -> ipaddr option =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input_arpv4 : t -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l connect : ethif -> [> `Error of error | `Ok of t ] Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 end =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is not included in =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 V1_LWT.IP Any hotfix for that? ------=_Part_1107140_1407820520.1428400080269 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I hav= e pinned tcpip 2.2.3 to opam and receive the following error when building = a network application (e.g. network in mirage-skeleton):

Error: Signature mismatch:
       Modules do not match:
         functo= r (C : V1.CLOCK) (T : V1_LWT.TIME) ->
 &nb= sp;         sig
           &nb= sp; type buffer =3D Cstruct.t
   &n= bsp;         type ethif =3D Stackv4= 1_E.t
       &n= bsp;     type ipaddr =3D Ipaddr.V4.t
           &n= bsp; type prefix =3D Ipaddr.V4.t
   = ;          type error =3D [ `U= nimplemented | `Unknown of string ]
  &n= bsp;          type 'a io =3D '= a Lwt.t
       =       type t =3D Ipv4.Make(Stackv41_E)(C)(T).t
         = ;    val disconnect : t -> unit io
            = type callback =3D src:ipaddr -> dst:ipaddr -> buffer -> unit io        &nb= sp;    val input :
  &nbs= p;            t ->= ;
        =        tcp:callback ->
           &nb= sp;   udp:callback ->
  &nb= sp;            defau= lt:(proto:int -> callback) -> buffer -> unit io
           &n= bsp; val allocate_frame :
    =            t ->
         &n= bsp;     dst:ipaddr -> proto:[ `ICMP | `TCP | `UDP ]= -> buffer * int
     =         val write : t -> buffer ->= buffer -> unit io
    &nbs= p;        val writev : t -> buffer -&= gt; buffer list -> unit io
   &n= bsp;         val checksum : buffer = -> buffer list -> int
   &nbs= p;         val get_source : t ->= dst:ipaddr -> ipaddr
    &= nbsp;        val set_ip : t -> ipaddr= -> unit io
      = ;       val get_ip : t -> ipaddr list
         =     val set_ip_netmask : t -> prefix -> unit io
         &n= bsp;   val get_ip_netmasks : t -> prefix list
           =   val set_ip_gateways : t -> ipaddr list -> unit io
          &n= bsp;  val get_ip_gateways : t -> ipaddr list
            = type uipaddr =3D Ipaddr.t
    = ;         val to_uipaddr : ipaddr -= > uipaddr
      &= nbsp;      val of_uipaddr : uipaddr -> ipaddr o= ption
       &n= bsp;     val input_arpv4 : t -> buffer -> unit io=
        &= nbsp;    val connect : ethif -> [> `Error of error | `= Ok of t ] Lwt.t
     &nbs= p;     end
   &= nbsp;   is not included in
  &= nbsp;      V1_LWT.IP

Any hotfix for that?
------=_Part_1107140_1407820520.1428400080269-- --===============1558379887057102191== 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 --===============1558379887057102191==-- From mirageos-devel-bounces@lists.xenproject.org Tue Apr 07 10:47:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 10:47:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfR2t-0000ca-Qu; Tue, 07 Apr 2015 10:47:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfR2s-0000cV-Ot for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 10:47:51 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id F6/98-13265-5D5B3255; Tue, 07 Apr 2015 10:47:49 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1428403667!14223358!1 X-Originating-IP: [98.138.229.97] X-SpamReason: No, hits=0.9 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21088 invoked from network); 7 Apr 2015 10:47:48 -0000 Received: from nm35-vm1.bullet.mail.ne1.yahoo.com (HELO nm35-vm1.bullet.mail.ne1.yahoo.com) (98.138.229.97) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 10:47:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1428403666; bh=7k7hGRcZFrVFTHQ0ZXg1ncI+EJ5/mYueQR2EosqJWVw=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=uKGqqHvMeFwPo2buFnTQOjZVxZkS86Ft3IoG4Tj/k3q02Amhsy9Cn6by172Y2Z8jaIJTmHnmg96dxcv40n5vF6XN5C1i3DjHyH38UTzb77GZUolC5DALJZeU4vFAlqAQzIQ7v6LcmRV/Rr5T9c70zPbjFHDxp7VPHhUNLI/FhpMoHpXNskj/D0MPCfmXO32bKC+2ofXxcIXutW7Z6aCxYdwfm99sGRr2Qd/oUWIu8REF4gwC0T7Dp/9Cl5AEYp04+rhyys70iKvhTAIKjTF+EI8lIDp2VEGkTS70VPK3A1/2pR0L83oTYeI35gY//MnH+r8sB55xyEXa3KowMDx5mA== Received: from [127.0.0.1] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 10:47:46 -0000 Received: from [98.138.100.112] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 Received: from [98.139.170.178] by tm103.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 Received: from [98.139.212.198] by tm21.bullet.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 Received: from [127.0.0.1] by omp1007.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 456702.24802.bm@omp1007.mail.bf1.yahoo.com X-YMail-OSG: z8oA26AVM1lxG0HU4Bj2fI7zY1Z5wYKAtUROZc.tMK1h5Zf3jGdhZREi2OcGuUt a2VFZT4kHZcbwWyvlAcGxo9kvawLyS._YXVv3hhYE.mwvqj.Qhy4tsB6pk.KHAPFr.ahhK6g6pgK FBBaS1fKSStmARY7vuayh0GoiqSHu.XGFrT2gChFQvQehDlugCp90rq9EaMunq53gWoR_Xvdemed EMOTFW3iS50lETJqqQgqKft4soU_eDlku4ru1SyV4x1fLchqfUIINlxKb2gA7sWBc_GjSaEWrG6y 4mXM8W0oMw3E1ZoOp5kpPQdRGqg13VQ_KpeBO02Oply6iZYXkrBf.7VXMVB5dLXHk74pQDvqiLKF 4C0nUgiNpyvq6rbXiOhPxgK4gtGzdgbBLBjj_vI3auACaR91U.0M.XYaM39jgXncXbWq.W1TCjPo QX4Rrb5biepnj1Sq65nn.hW4N.YJVu0ujZx.zaCN8w09JJuscqoQpExIjbMaGoegvKR8- Received: by 76.13.26.108; Tue, 07 Apr 2015 10:45:02 +0000 Date: Tue, 7 Apr 2015 10:45:01 +0000 (UTC) From: Ania Skorupa To: Mirageos-devel Message-ID: <856668176.1160714.1428403501722.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <945649343.1107141.1428400080274.JavaMail.yahoo@mail.yahoo.com> References: <945649343.1107141.1428400080274.JavaMail.yahoo@mail.yahoo.com> MIME-Version: 1.0 Content-Length: 12842 Subject: Re: [MirageOS-devel] Signature mismatch in tcpip 2.2.3 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4155368310056275436==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4155368310056275436== Content-Type: multipart/alternative; boundary="----=_Part_1160713_1596753481.1428403501719" Content-Length: 12298 ------=_Part_1160713_1596753481.1428403501719 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ah, I cloned tcpip from its github repository. Although the version is 2.4.= 0 based on _oasis, opam installs it as 2.2.3. =20 On Tuesday, April 7, 2015 9:48 AM, Ania Skorupa wrote: =20 I have pinned tcpip 2.2.3 to opam and receive the following error when bui= lding a network application (e.g. network in mirage-skeleton): Error: Signature mismatch: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Modules do not match: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functor (C : V1.CLOCK) (T = : V1_LWT.TIME) -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sig =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe buffer =3D Cstruct.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ethif =3D Stackv41_E.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ipaddr =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe prefix =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe error =3D [ `Unimplemented | `Unknown of string ] =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe 'a io =3D 'a Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe t =3D Ipv4.Make(Stackv41_E)(C)(T).t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l disconnect : t -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe callback =3D src:ipaddr -> dst:ipaddr -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 tcp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 udp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 default:(proto:int -> callback) -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l allocate_frame : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 dst:ipaddr -> proto:[ `ICMP | `TCP | `UDP ] -> buffer * int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l write : t -> buffer -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l writev : t -> buffer -> buffer list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l checksum : buffer -> buffer list -> int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_source : t -> dst:ipaddr -> ipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip : t -> ipaddr -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_netmask : t -> prefix -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_netmasks : t -> prefix list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_gateways : t -> ipaddr list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_gateways : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe uipaddr =3D Ipaddr.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l to_uipaddr : ipaddr -> uipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l of_uipaddr : uipaddr -> ipaddr option =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input_arpv4 : t -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l connect : ethif -> [> `Error of error | `Ok of t ] Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 end =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is not included in =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 V1_LWT.IP Any hotfix for that? ------=_Part_1160713_1596753481.1428403501719 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ah, I= cloned tcpip from its github repository. Although the version is 2.4.0 bas= ed on _oasis, opam installs it as 2.2.3.



On Tuesday, April 7, 2015 9:48 AM, Ania Skorupa &= lt;ania.skorupa@yahoo.com> wrote:


I have pinned tcpip 2.2.3 t= o opam and receive the following error when building a network application = (e.g. network in mirage-skeleton):

Error: Signature mismatch:
       Modules = do not match:
    = ;     functor (C : V1.CLOCK) (T : V1_LWT.TIME) ->      &nb= sp;    sig
  = ;           type buffer = =3D Cstruct.t
    = ;         type ethif =3D Stackv41_E= .t
     &nbs= p;       type ipaddr =3D Ipaddr.V4.t
       &nb= sp;     type prefix =3D Ipaddr.V4.t
         &n= bsp;   type error =3D [ `Unimplemented | `Unknown of string ]
      &nbs= p;      type 'a io =3D 'a Lwt.t
         &= nbsp;   type t =3D Ipv4.Make(Stackv41_E)(C)(T).t
         = ;    val disconnect : t -> unit io
          = ;   type callback =3D src:ipaddr -> dst:ipaddr -> buffer -&= gt; unit io
    &= nbsp;        val input :
        &nbs= p;      t ->
            = ;   tcp:callback ->
&nbs= p;            &= nbsp; udp:callback ->
  =              de= fault:(proto:int -> callback) -> buffer -> unit io
        &nbs= p;    val allocate_frame :
           &nbs= p;   t ->
  &n= bsp;            dst:= ipaddr -> proto:[ `ICMP | `TCP | `UDP ] -> buffer * int
        &n= bsp;    val write : t -> buffer -> buffer -> unit i= o
      = ;       val writev : t -> buffer -> buf= fer list -> unit io
  &n= bsp;          val checksum : b= uffer -> buffer list -> int
&nb= sp;            val g= et_source : t -> dst:ipaddr -> ipaddr
           &n= bsp; val set_ip : t -> ipaddr -> unit io
           = ;  val get_ip : t -> ipaddr list
            = ; val set_ip_netmask : t -> prefix -> unit io
          =    val get_ip_netmasks : t -> prefix list
         &n= bsp;   val set_ip_gateways : t -> ipaddr list -> unit io      &nb= sp;      val get_ip_gateways : t -> ipaddr list=
      =        type uipaddr =3D Ipaddr.t
        &= nbsp;    val to_uipaddr : ipaddr -> uipaddr
        &n= bsp;    val of_uipaddr : uipaddr -> ipaddr option
       &n= bsp;     val input_arpv4 : t -> buffer -> unit io=
      =        val connect : ethif -> [> `Error= of error | `Ok of t ] Lwt.t
 &n= bsp;         end
       is not included in=
      =    V1_LWT.IP

Any hotfi= x for that?


------=_Part_1160713_1596753481.1428403501719-- --===============4155368310056275436== 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 --===============4155368310056275436==-- From mirageos-devel-bounces@lists.xenproject.org Tue Apr 07 10:47:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 10:47:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfR2t-0000ca-Qu; Tue, 07 Apr 2015 10:47:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfR2s-0000cV-Ot for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 10:47:51 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id F6/98-13265-5D5B3255; Tue, 07 Apr 2015 10:47:49 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1428403667!14223358!1 X-Originating-IP: [98.138.229.97] X-SpamReason: No, hits=0.9 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21088 invoked from network); 7 Apr 2015 10:47:48 -0000 Received: from nm35-vm1.bullet.mail.ne1.yahoo.com (HELO nm35-vm1.bullet.mail.ne1.yahoo.com) (98.138.229.97) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 10:47:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1428403666; bh=7k7hGRcZFrVFTHQ0ZXg1ncI+EJ5/mYueQR2EosqJWVw=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=uKGqqHvMeFwPo2buFnTQOjZVxZkS86Ft3IoG4Tj/k3q02Amhsy9Cn6by172Y2Z8jaIJTmHnmg96dxcv40n5vF6XN5C1i3DjHyH38UTzb77GZUolC5DALJZeU4vFAlqAQzIQ7v6LcmRV/Rr5T9c70zPbjFHDxp7VPHhUNLI/FhpMoHpXNskj/D0MPCfmXO32bKC+2ofXxcIXutW7Z6aCxYdwfm99sGRr2Qd/oUWIu8REF4gwC0T7Dp/9Cl5AEYp04+rhyys70iKvhTAIKjTF+EI8lIDp2VEGkTS70VPK3A1/2pR0L83oTYeI35gY//MnH+r8sB55xyEXa3KowMDx5mA== Received: from [127.0.0.1] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 10:47:46 -0000 Received: from [98.138.100.112] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 Received: from [98.139.170.178] by tm103.bullet.mail.ne1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 Received: from [98.139.212.198] by tm21.bullet.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 Received: from [127.0.0.1] by omp1007.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 10:45:02 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 456702.24802.bm@omp1007.mail.bf1.yahoo.com X-YMail-OSG: z8oA26AVM1lxG0HU4Bj2fI7zY1Z5wYKAtUROZc.tMK1h5Zf3jGdhZREi2OcGuUt a2VFZT4kHZcbwWyvlAcGxo9kvawLyS._YXVv3hhYE.mwvqj.Qhy4tsB6pk.KHAPFr.ahhK6g6pgK FBBaS1fKSStmARY7vuayh0GoiqSHu.XGFrT2gChFQvQehDlugCp90rq9EaMunq53gWoR_Xvdemed EMOTFW3iS50lETJqqQgqKft4soU_eDlku4ru1SyV4x1fLchqfUIINlxKb2gA7sWBc_GjSaEWrG6y 4mXM8W0oMw3E1ZoOp5kpPQdRGqg13VQ_KpeBO02Oply6iZYXkrBf.7VXMVB5dLXHk74pQDvqiLKF 4C0nUgiNpyvq6rbXiOhPxgK4gtGzdgbBLBjj_vI3auACaR91U.0M.XYaM39jgXncXbWq.W1TCjPo QX4Rrb5biepnj1Sq65nn.hW4N.YJVu0ujZx.zaCN8w09JJuscqoQpExIjbMaGoegvKR8- Received: by 76.13.26.108; Tue, 07 Apr 2015 10:45:02 +0000 Date: Tue, 7 Apr 2015 10:45:01 +0000 (UTC) From: Ania Skorupa To: Mirageos-devel Message-ID: <856668176.1160714.1428403501722.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <945649343.1107141.1428400080274.JavaMail.yahoo@mail.yahoo.com> References: <945649343.1107141.1428400080274.JavaMail.yahoo@mail.yahoo.com> MIME-Version: 1.0 Content-Length: 12842 Subject: Re: [MirageOS-devel] Signature mismatch in tcpip 2.2.3 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4155368310056275436==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4155368310056275436== Content-Type: multipart/alternative; boundary="----=_Part_1160713_1596753481.1428403501719" Content-Length: 12298 ------=_Part_1160713_1596753481.1428403501719 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ah, I cloned tcpip from its github repository. Although the version is 2.4.= 0 based on _oasis, opam installs it as 2.2.3. =20 On Tuesday, April 7, 2015 9:48 AM, Ania Skorupa wrote: =20 I have pinned tcpip 2.2.3 to opam and receive the following error when bui= lding a network application (e.g. network in mirage-skeleton): Error: Signature mismatch: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Modules do not match: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functor (C : V1.CLOCK) (T = : V1_LWT.TIME) -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sig =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe buffer =3D Cstruct.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ethif =3D Stackv41_E.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe ipaddr =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe prefix =3D Ipaddr.V4.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe error =3D [ `Unimplemented | `Unknown of string ] =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe 'a io =3D 'a Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe t =3D Ipv4.Make(Stackv41_E)(C)(T).t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l disconnect : t -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe callback =3D src:ipaddr -> dst:ipaddr -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 tcp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 udp:callback -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 default:(proto:int -> callback) -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l allocate_frame : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 t -> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 dst:ipaddr -> proto:[ `ICMP | `TCP | `UDP ] -> buffer * int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l write : t -> buffer -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l writev : t -> buffer -> buffer list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l checksum : buffer -> buffer list -> int =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_source : t -> dst:ipaddr -> ipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip : t -> ipaddr -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_netmask : t -> prefix -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_netmasks : t -> prefix list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l set_ip_gateways : t -> ipaddr list -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l get_ip_gateways : t -> ipaddr list =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ty= pe uipaddr =3D Ipaddr.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l to_uipaddr : ipaddr -> uipaddr =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l of_uipaddr : uipaddr -> ipaddr option =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l input_arpv4 : t -> buffer -> unit io =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 va= l connect : ethif -> [> `Error of error | `Ok of t ] Lwt.t =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 end =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is not included in =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 V1_LWT.IP Any hotfix for that? ------=_Part_1160713_1596753481.1428403501719 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ah, I= cloned tcpip from its github repository. Although the version is 2.4.0 bas= ed on _oasis, opam installs it as 2.2.3.



On Tuesday, April 7, 2015 9:48 AM, Ania Skorupa &= lt;ania.skorupa@yahoo.com> wrote:


I have pinned tcpip 2.2.3 t= o opam and receive the following error when building a network application = (e.g. network in mirage-skeleton):

Error: Signature mismatch:
       Modules = do not match:
    = ;     functor (C : V1.CLOCK) (T : V1_LWT.TIME) ->      &nb= sp;    sig
  = ;           type buffer = =3D Cstruct.t
    = ;         type ethif =3D Stackv41_E= .t
     &nbs= p;       type ipaddr =3D Ipaddr.V4.t
       &nb= sp;     type prefix =3D Ipaddr.V4.t
         &n= bsp;   type error =3D [ `Unimplemented | `Unknown of string ]
      &nbs= p;      type 'a io =3D 'a Lwt.t
         &= nbsp;   type t =3D Ipv4.Make(Stackv41_E)(C)(T).t
         = ;    val disconnect : t -> unit io
          = ;   type callback =3D src:ipaddr -> dst:ipaddr -> buffer -&= gt; unit io
    &= nbsp;        val input :
        &nbs= p;      t ->
            = ;   tcp:callback ->
&nbs= p;            &= nbsp; udp:callback ->
  =              de= fault:(proto:int -> callback) -> buffer -> unit io
        &nbs= p;    val allocate_frame :
           &nbs= p;   t ->
  &n= bsp;            dst:= ipaddr -> proto:[ `ICMP | `TCP | `UDP ] -> buffer * int
        &n= bsp;    val write : t -> buffer -> buffer -> unit i= o
      = ;       val writev : t -> buffer -> buf= fer list -> unit io
  &n= bsp;          val checksum : b= uffer -> buffer list -> int
&nb= sp;            val g= et_source : t -> dst:ipaddr -> ipaddr
           &n= bsp; val set_ip : t -> ipaddr -> unit io
           = ;  val get_ip : t -> ipaddr list
            = ; val set_ip_netmask : t -> prefix -> unit io
          =    val get_ip_netmasks : t -> prefix list
         &n= bsp;   val set_ip_gateways : t -> ipaddr list -> unit io      &nb= sp;      val get_ip_gateways : t -> ipaddr list=
      =        type uipaddr =3D Ipaddr.t
        &= nbsp;    val to_uipaddr : ipaddr -> uipaddr
        &n= bsp;    val of_uipaddr : uipaddr -> ipaddr option
       &n= bsp;     val input_arpv4 : t -> buffer -> unit io=
      =        val connect : ethif -> [> `Error= of error | `Ok of t ] Lwt.t
 &n= bsp;         end
       is not included in=
      =    V1_LWT.IP

Any hotfi= x for that?


------=_Part_1160713_1596753481.1428403501719-- --===============4155368310056275436== 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 --===============4155368310056275436==-- From mirageos-devel-bounces@lists.xenproject.org Tue Apr 07 11:15:28 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 11:15: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 1YfRTa-00030J-4V; Tue, 07 Apr 2015 11:15:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfRTZ-00030B-1d for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 11:15:25 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id AD/25-13722-C4CB3255; Tue, 07 Apr 2015 11:15:24 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1428405323!12602787!1 X-Originating-IP: [209.85.217.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29832 invoked from network); 7 Apr 2015 11:15:23 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 11:15:23 -0000 Received: by lbbqq2 with SMTP id qq2so31198385lbb.3 for ; Tue, 07 Apr 2015 04:15:22 -0700 (PDT) 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:content-transfer-encoding; bh=qUYGBD4lRrRDJWjSgIpEFYGFpx2pI+SKmxIB+EpsbvI=; b=CPGkpbWmBI9+2h46QylePafFayCA+070FPW5NM7oNh/33gFJKfdV5zRqEO4cSw7ujH o0IMGagYthv1GqjCNoeU3V0vqhDKvnV1AgeHhbGK42iYGgk5USHCVg0VV/EbyiLIvytx 1zMeQ24BhMrXB578G2iy8Z5/OsMR+qrtjkCrJlyASjQO6z59WT7B6ZKiaYuw1yMR9OeP 3tV14JGxJBfzdf9OmfnLn+UAm1/QRMJVpjEQcRpb4a+Tcxae1+k//J/0bRYwM0R5ho6D UHPOZ3d1f3V7L7iT54LRv1V7k0ovLTmfJ3zmx1URoNKJMVqMNV6G0ZuZ3HV1a6S+Lbu6 5r2A== MIME-Version: 1.0 X-Received: by 10.112.97.202 with SMTP id ec10mr17561334lbb.4.1428405322625; Tue, 07 Apr 2015 04:15:22 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Tue, 7 Apr 2015 04:15:22 -0700 (PDT) In-Reply-To: References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> Date: Tue, 7 Apr 2015 12:15:22 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 30 March 2015 at 17:49, Thomas Gazagnaire wrote: >>>> Not sure how to expose that nicely to the user though... maybe allowing to specify a "parent" optional argument to merge/update/rebase. >> >> That would be useful. I've been avoiding the "Private" API so far, but >> maybe I should start using it. > > I've just open a new PR to fix that: https://github.com/mirage/irmin/pull/178 > > I've exposed `View.parents` and `View.set_parents` to do that. I'm not very happy with that API: on one hand, it would be much better to have immutable views (and have `with_parents` to modify the parents), but on the other hand, the current APIs is nice because it is a subset of Irmin.S so I kept exposing the side-effects... >>> You can only create a view from one store and apply it in the other: the history of commit will be kept as expected. See: >>> >>> https://github.com/samoht/dog/blob/master/lib/dog.ml#L247 >>> >>> You can try to use that to merge views from different branches, not sure how practical this is though. >> >> The basic logic I have is roughly: >> >> 1. git checkout base >> 2. (apply modification) >> 3. UPDATE=$(git commit-tree -p base) >> 4. git checkout master >> 5. git-merge -s custom $UPDATE >> >> Where "custom" should be my app-specific merge logic that works on >> whole trees rather than individual files. > > So now you should be able to create a view, do some stuff on it, give it the parents you need and save it. I'm not sure how to use this. It looks like parents is only used in merge_path. How do I use it with update_path? Ideally, I think I want something like: BC.make_head : Irmin.config -> ('a -> Irmin.task) -> parents:head list -> msg:'a -> View.t -> ('a -> t) Lwt.t to implement CueKeeper's API: module Commit : sig type t val commit : parents:t list -> Staging.t -> msg:string -> t Lwt.t How can I take two commits, generate a view (manually) with the results of my custom merge, and then add the result as a new commit with both of the original parents? >> Currently, I merge to create a new commit, test it, and then do a >> fast-forward to update the branch to include the merge if the test >> passes. But if I can use custom merge code, then it would be OK to >> merge directly to the branch when my merge code returns, since it will >> already have had a chance to test it. > > In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. Thanks! [ As noted elsewhere, it would be useful to distinguish the case where it's already up-to-date (success; no futher action needed) from the case where it's not an ancestor (failure; retry merge with new head). ] > Let me know if you need something else (I'm still working on the right way to fix the watch API). > > Best, > Thomas > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 07 11:15:28 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 11:15: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 1YfRTa-00030J-4V; Tue, 07 Apr 2015 11:15:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfRTZ-00030B-1d for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 11:15:25 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id AD/25-13722-C4CB3255; Tue, 07 Apr 2015 11:15:24 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1428405323!12602787!1 X-Originating-IP: [209.85.217.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29832 invoked from network); 7 Apr 2015 11:15:23 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 11:15:23 -0000 Received: by lbbqq2 with SMTP id qq2so31198385lbb.3 for ; Tue, 07 Apr 2015 04:15:22 -0700 (PDT) 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:content-transfer-encoding; bh=qUYGBD4lRrRDJWjSgIpEFYGFpx2pI+SKmxIB+EpsbvI=; b=CPGkpbWmBI9+2h46QylePafFayCA+070FPW5NM7oNh/33gFJKfdV5zRqEO4cSw7ujH o0IMGagYthv1GqjCNoeU3V0vqhDKvnV1AgeHhbGK42iYGgk5USHCVg0VV/EbyiLIvytx 1zMeQ24BhMrXB578G2iy8Z5/OsMR+qrtjkCrJlyASjQO6z59WT7B6ZKiaYuw1yMR9OeP 3tV14JGxJBfzdf9OmfnLn+UAm1/QRMJVpjEQcRpb4a+Tcxae1+k//J/0bRYwM0R5ho6D UHPOZ3d1f3V7L7iT54LRv1V7k0ovLTmfJ3zmx1URoNKJMVqMNV6G0ZuZ3HV1a6S+Lbu6 5r2A== MIME-Version: 1.0 X-Received: by 10.112.97.202 with SMTP id ec10mr17561334lbb.4.1428405322625; Tue, 07 Apr 2015 04:15:22 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Tue, 7 Apr 2015 04:15:22 -0700 (PDT) In-Reply-To: References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> Date: Tue, 7 Apr 2015 12:15:22 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 30 March 2015 at 17:49, Thomas Gazagnaire wrote: >>>> Not sure how to expose that nicely to the user though... maybe allowing to specify a "parent" optional argument to merge/update/rebase. >> >> That would be useful. I've been avoiding the "Private" API so far, but >> maybe I should start using it. > > I've just open a new PR to fix that: https://github.com/mirage/irmin/pull/178 > > I've exposed `View.parents` and `View.set_parents` to do that. I'm not very happy with that API: on one hand, it would be much better to have immutable views (and have `with_parents` to modify the parents), but on the other hand, the current APIs is nice because it is a subset of Irmin.S so I kept exposing the side-effects... >>> You can only create a view from one store and apply it in the other: the history of commit will be kept as expected. See: >>> >>> https://github.com/samoht/dog/blob/master/lib/dog.ml#L247 >>> >>> You can try to use that to merge views from different branches, not sure how practical this is though. >> >> The basic logic I have is roughly: >> >> 1. git checkout base >> 2. (apply modification) >> 3. UPDATE=$(git commit-tree -p base) >> 4. git checkout master >> 5. git-merge -s custom $UPDATE >> >> Where "custom" should be my app-specific merge logic that works on >> whole trees rather than individual files. > > So now you should be able to create a view, do some stuff on it, give it the parents you need and save it. I'm not sure how to use this. It looks like parents is only used in merge_path. How do I use it with update_path? Ideally, I think I want something like: BC.make_head : Irmin.config -> ('a -> Irmin.task) -> parents:head list -> msg:'a -> View.t -> ('a -> t) Lwt.t to implement CueKeeper's API: module Commit : sig type t val commit : parents:t list -> Staging.t -> msg:string -> t Lwt.t How can I take two commits, generate a view (manually) with the results of my custom merge, and then add the result as a new commit with both of the original parents? >> Currently, I merge to create a new commit, test it, and then do a >> fast-forward to update the branch to include the merge if the test >> passes. But if I can use custom merge code, then it would be OK to >> merge directly to the branch when my merge code returns, since it will >> already have had a chance to test it. > > In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. Thanks! [ As noted elsewhere, it would be useful to distinguish the case where it's already up-to-date (success; no futher action needed) from the case where it's not an ancestor (failure; retry merge with new head). ] > Let me know if you need something else (I'm still working on the right way to fix the watch API). > > Best, > Thomas > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 07 13:20:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 13:20: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 1YfTQ6-0004S8-57; Tue, 07 Apr 2015 13:19:58 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfTQ4-0004S3-Ls for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 13:19:56 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id F4/6C-16511-C79D3255; Tue, 07 Apr 2015 13:19:56 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1428412795!16046293!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5270 invoked from network); 7 Apr 2015 13:19:55 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 13:19:55 -0000 Received: by wiun10 with SMTP id n10so18371534wiu.1 for ; Tue, 07 Apr 2015 06:19:55 -0700 (PDT) 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=sxik9gf5Cyi8+x4t41zf/StIG+tj/CaH4VlapNLLU1o=; b=yL+RXR322rs2T3VRA8AqPnyHqWvH/Y0mpQYSNpjnhV4EcAT3/flt0ExuwrS16UfTOl DmZBlS3kCgis7oz9+CMRjZy0oZQP4BxMNNw956NUgLbaIEkVkPjK/bx1LZ35US2aTuXL tG6PmPAGESm9ypBBWZrFptMXzClmJ+E2RZiiBc7DbtnHrmx6rxEVPMCGJx+tIOHhH3z0 F1cToBn66/E2LhHUzovYw3ohy1IEQq62eMDm/7MjR/YWhrZrOM5yKCnWoQl0XB2WU8fQ qjxeaPJtSYY4jSQZndbBwUjbQbdC4F8IDzYRIbO2dnBsxE/v7pyUki6ZgLUQVHyuFs56 +uuA== X-Received: by 10.194.57.170 with SMTP id j10mr40766723wjq.102.1428412794825; Tue, 07 Apr 2015 06:19:54 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id fu1sm11006644wic.12.2015.04.07.06.19.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Apr 2015 06:19:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 7 Apr 2015 15:19:52 +0200 Message-Id: <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 how to use this. It looks like parents is only used in > merge_path. How do I use it with update_path? > > Ideally, I think I want something like: > > BC.make_head : > Irmin.config -> ('a -> Irmin.task) -> parents:head list -> > msg:'a -> View.t -> ('a -> t) Lwt.t > > to implement CueKeeper's API: > > module Commit : sig > type t > val commit : > parents:t list -> > Staging.t -> > msg:string -> > t Lwt.t > > How can I take two commits, generate a view (manually) with the > results of my custom merge, and then add the result as a new commit > with both of the original parents? Something like: let commit ~parents staging ~msg = match staging.Staging.commit with | None -> assert false | Some t -> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> {t with c_store = tmp_branch} I'll see if I can add your `make_head` function. Thomas > >>> Currently, I merge to create a new commit, test it, and then do a >>> fast-forward to update the branch to include the merge if the test >>> passes. But if I can use custom merge code, then it would be OK to >>> merge directly to the branch when my merge code returns, since it will >>> already have had a chance to test it. >> >> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. > > Thanks! [ As noted elsewhere, it would be useful to distinguish the > case where it's already up-to-date (success; no futher action needed) > from the case where it's not an ancestor (failure; retry merge with > new head). ] > >> Let me know if you need something else (I'm still working on the right way to fix the watch API). >> >> Best, >> Thomas >> > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 07 13:20:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 13:20: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 1YfTQ6-0004S8-57; Tue, 07 Apr 2015 13:19:58 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfTQ4-0004S3-Ls for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 13:19:56 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id F4/6C-16511-C79D3255; Tue, 07 Apr 2015 13:19:56 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1428412795!16046293!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5270 invoked from network); 7 Apr 2015 13:19:55 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 13:19:55 -0000 Received: by wiun10 with SMTP id n10so18371534wiu.1 for ; Tue, 07 Apr 2015 06:19:55 -0700 (PDT) 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=sxik9gf5Cyi8+x4t41zf/StIG+tj/CaH4VlapNLLU1o=; b=yL+RXR322rs2T3VRA8AqPnyHqWvH/Y0mpQYSNpjnhV4EcAT3/flt0ExuwrS16UfTOl DmZBlS3kCgis7oz9+CMRjZy0oZQP4BxMNNw956NUgLbaIEkVkPjK/bx1LZ35US2aTuXL tG6PmPAGESm9ypBBWZrFptMXzClmJ+E2RZiiBc7DbtnHrmx6rxEVPMCGJx+tIOHhH3z0 F1cToBn66/E2LhHUzovYw3ohy1IEQq62eMDm/7MjR/YWhrZrOM5yKCnWoQl0XB2WU8fQ qjxeaPJtSYY4jSQZndbBwUjbQbdC4F8IDzYRIbO2dnBsxE/v7pyUki6ZgLUQVHyuFs56 +uuA== X-Received: by 10.194.57.170 with SMTP id j10mr40766723wjq.102.1428412794825; Tue, 07 Apr 2015 06:19:54 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id fu1sm11006644wic.12.2015.04.07.06.19.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Apr 2015 06:19:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 7 Apr 2015 15:19:52 +0200 Message-Id: <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 how to use this. It looks like parents is only used in > merge_path. How do I use it with update_path? > > Ideally, I think I want something like: > > BC.make_head : > Irmin.config -> ('a -> Irmin.task) -> parents:head list -> > msg:'a -> View.t -> ('a -> t) Lwt.t > > to implement CueKeeper's API: > > module Commit : sig > type t > val commit : > parents:t list -> > Staging.t -> > msg:string -> > t Lwt.t > > How can I take two commits, generate a view (manually) with the > results of my custom merge, and then add the result as a new commit > with both of the original parents? Something like: let commit ~parents staging ~msg = match staging.Staging.commit with | None -> assert false | Some t -> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> {t with c_store = tmp_branch} I'll see if I can add your `make_head` function. Thomas > >>> Currently, I merge to create a new commit, test it, and then do a >>> fast-forward to update the branch to include the merge if the test >>> passes. But if I can use custom merge code, then it would be OK to >>> merge directly to the branch when my merge code returns, since it will >>> already have had a chance to test it. >> >> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. > > Thanks! [ As noted elsewhere, it would be useful to distinguish the > case where it's already up-to-date (success; no futher action needed) > from the case where it's not an ancestor (failure; retry merge with > new head). ] > >> Let me know if you need something else (I'm still working on the right way to fix the watch API). >> >> Best, >> Thomas >> > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 07 14:13:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 14:13:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfUFS-00006J-FE; Tue, 07 Apr 2015 14:13:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfUFQ-00006E-La for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 14:13:00 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id BA/20-18531-BE5E3255; Tue, 07 Apr 2015 14:12:59 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1428415978!14305591!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13674 invoked from network); 7 Apr 2015 14:12:59 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 14:12:59 -0000 Received: by lagv1 with SMTP id v1so43105644lag.3 for ; Tue, 07 Apr 2015 07:12:58 -0700 (PDT) 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=XWaetyauzf89NSVdwufa3NhBD0EgSRsU/72zmWSNt6g=; b=tYOF985qivVVZ31GKIvSXkns921ymIHSpbazSIkLohHQ1WdL7wlnT6EZ+DtQbF7n3L vX1n1JViwwquMC5bKA6XraAYsPvDai2P+gxI175zu3Q5zmAoOlfJjsKg905/N/YiXKqV RkyC923HC5Wcbnzy6WHS7RbpT0mNjXNLQzJr9m4V3emG+gZymJZC2rv2g+6LTAkAMxH8 97RWeTpasdDO+mO/fhK3A8joi7dSNU6InQp4E1yFZMBTi2brc7xM0RQdSTA5pDr6hT3Q EccEbc1v19eX5ZAKF5GfM2qpCg6KPJ8asBtogiNDx+/FmxHwFs21Gp9R609Pe1Thal9t jLhw== MIME-Version: 1.0 X-Received: by 10.112.13.73 with SMTP id f9mr16652161lbc.124.1428415978197; Tue, 07 Apr 2015 07:12:58 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Tue, 7 Apr 2015 07:12:58 -0700 (PDT) In-Reply-To: <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> Date: Tue, 7 Apr 2015 15:12:58 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 7 April 2015 at 14:19, Thomas Gazagnaire wrote: >> I'm not sure how to use this. It looks like parents is only used in >> merge_path. How do I use it with update_path? >> >> Ideally, I think I want something like: >> >> BC.make_head : >> Irmin.config -> ('a -> Irmin.task) -> parents:head list -> >> msg:'a -> View.t -> ('a -> t) Lwt.t >> >> to implement CueKeeper's API: >> >> module Commit : sig >> type t >> val commit : >> parents:t list -> >> Staging.t -> >> msg:string -> >> t Lwt.t >> >> How can I take two commits, generate a view (manually) with the >> results of my custom merge, and then add the result as a new commit >> with both of the original parents? > > Something like: > > let commit ~parents staging ~msg = > match staging.Staging.commit with > | None -> assert false > | Some t -> > I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> > (* THE ONLY CHANGE *) V.set_parents Staging.view parents; > V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> > {t with c_store = tmp_branch} It doesn't seem to work. I tested with this code (on my "test_merging" branch): https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d Git.Commit.checkout base >>= fun stage -> Git.Staging.update stage ["foo"] "a" >>= fun () -> Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> Git.Staging.update stage ["foo"] "b" >>= fun () -> Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> Git.Staging.update stage ["foo"] "merged" >>= fun () -> Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> Git.Branch.fast_forward_to master result >>= function For testing, it uses the Git backend with the directory "test_db". Looking at the result with gitk, I have an initial commit containing "orig" with a direct child "Merge" containing "merged". [ I also had to expose "VIEW.head = S.head" in Irmin: https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 and I modified your code slightly to make "parents" optional and to be a Commit.t, but that shouldn't make any difference I think. ] > I'll see if I can add your `make_head` function. > > Thomas > >> >>>> Currently, I merge to create a new commit, test it, and then do a >>>> fast-forward to update the branch to include the merge if the test >>>> passes. But if I can use custom merge code, then it would be OK to >>>> merge directly to the branch when my merge code returns, since it will >>>> already have had a chance to test it. >>> >>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >> >> Thanks! [ As noted elsewhere, it would be useful to distinguish the >> case where it's already up-to-date (success; no futher action needed) >> from the case where it's not an ancestor (failure; retry merge with >> new head). ] >> >>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>> >>> Best, >>> Thomas >>> >> >> >> >> -- >> Dr Thomas Leonard http://0install.net/ >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 07 14:13:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Apr 2015 14:13:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfUFS-00006J-FE; Tue, 07 Apr 2015 14:13:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfUFQ-00006E-La for mirageos-devel@lists.xenproject.org; Tue, 07 Apr 2015 14:13:00 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id BA/20-18531-BE5E3255; Tue, 07 Apr 2015 14:12:59 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1428415978!14305591!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13674 invoked from network); 7 Apr 2015 14:12:59 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2015 14:12:59 -0000 Received: by lagv1 with SMTP id v1so43105644lag.3 for ; Tue, 07 Apr 2015 07:12:58 -0700 (PDT) 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=XWaetyauzf89NSVdwufa3NhBD0EgSRsU/72zmWSNt6g=; b=tYOF985qivVVZ31GKIvSXkns921ymIHSpbazSIkLohHQ1WdL7wlnT6EZ+DtQbF7n3L vX1n1JViwwquMC5bKA6XraAYsPvDai2P+gxI175zu3Q5zmAoOlfJjsKg905/N/YiXKqV RkyC923HC5Wcbnzy6WHS7RbpT0mNjXNLQzJr9m4V3emG+gZymJZC2rv2g+6LTAkAMxH8 97RWeTpasdDO+mO/fhK3A8joi7dSNU6InQp4E1yFZMBTi2brc7xM0RQdSTA5pDr6hT3Q EccEbc1v19eX5ZAKF5GfM2qpCg6KPJ8asBtogiNDx+/FmxHwFs21Gp9R609Pe1Thal9t jLhw== MIME-Version: 1.0 X-Received: by 10.112.13.73 with SMTP id f9mr16652161lbc.124.1428415978197; Tue, 07 Apr 2015 07:12:58 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Tue, 7 Apr 2015 07:12:58 -0700 (PDT) In-Reply-To: <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> Date: Tue, 7 Apr 2015 15:12:58 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 7 April 2015 at 14:19, Thomas Gazagnaire wrote: >> I'm not sure how to use this. It looks like parents is only used in >> merge_path. How do I use it with update_path? >> >> Ideally, I think I want something like: >> >> BC.make_head : >> Irmin.config -> ('a -> Irmin.task) -> parents:head list -> >> msg:'a -> View.t -> ('a -> t) Lwt.t >> >> to implement CueKeeper's API: >> >> module Commit : sig >> type t >> val commit : >> parents:t list -> >> Staging.t -> >> msg:string -> >> t Lwt.t >> >> How can I take two commits, generate a view (manually) with the >> results of my custom merge, and then add the result as a new commit >> with both of the original parents? > > Something like: > > let commit ~parents staging ~msg = > match staging.Staging.commit with > | None -> assert false > | Some t -> > I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> > (* THE ONLY CHANGE *) V.set_parents Staging.view parents; > V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> > {t with c_store = tmp_branch} It doesn't seem to work. I tested with this code (on my "test_merging" branch): https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d Git.Commit.checkout base >>= fun stage -> Git.Staging.update stage ["foo"] "a" >>= fun () -> Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> Git.Staging.update stage ["foo"] "b" >>= fun () -> Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> Git.Staging.update stage ["foo"] "merged" >>= fun () -> Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> Git.Branch.fast_forward_to master result >>= function For testing, it uses the Git backend with the directory "test_db". Looking at the result with gitk, I have an initial commit containing "orig" with a direct child "Merge" containing "merged". [ I also had to expose "VIEW.head = S.head" in Irmin: https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 and I modified your code slightly to make "parents" optional and to be a Commit.t, but that shouldn't make any difference I think. ] > I'll see if I can add your `make_head` function. > > Thomas > >> >>>> Currently, I merge to create a new commit, test it, and then do a >>>> fast-forward to update the branch to include the merge if the test >>>> passes. But if I can use custom merge code, then it would be OK to >>>> merge directly to the branch when my merge code returns, since it will >>>> already have had a chance to test it. >>> >>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >> >> Thanks! [ As noted elsewhere, it would be useful to distinguish the >> case where it's already up-to-date (success; no futher action needed) >> from the case where it's not an ancestor (failure; retry merge with >> new head). ] >> >>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>> >>> Best, >>> Thomas >>> >> >> >> >> -- >> Dr Thomas Leonard http://0install.net/ >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 08 11:38:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Apr 2015 11:38:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfoJ8-0006h0-8l; Wed, 08 Apr 2015 11:38:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfoJ7-0006gr-6u for mirageos-devel@lists.xenproject.org; Wed, 08 Apr 2015 11:38:09 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id CA/B4-02119-02315255; Wed, 08 Apr 2015 11:38:08 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1428493086!10286552!1 X-Originating-IP: [209.85.213.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25543 invoked from network); 8 Apr 2015 11:38:07 -0000 Received: from mail-ig0-f178.google.com (HELO mail-ig0-f178.google.com) (209.85.213.178) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Apr 2015 11:38:07 -0000 Received: by iget9 with SMTP id t9so27451999ige.1 for ; Wed, 08 Apr 2015 04:38:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4mRWVKjDNpJ/x2tphhGWwbwbr7Sfj1dWuZdCkPUoTZg=; b=C0EwUjKjn1R2I2An8K7Rfr0zBCCWh1rMGho6C6wCKJtTb4KnqjxsRpwv9HUKJgtkK5 eY4SqMZFNxg3vAGBevk76CLpoATfvgrTmijpDc5KjR74LE1o1hPMkAgzJ2ZVuUf9GM9W XbSI1JAWe+I5/3cMAH1A10O7fuUDGJ75EiLgnrDJRKy281VzelYHZ96bU3YmgIpQ2oXk niViwJ1KKH2+N1KbeLAOAOXpP4AipVdeS5iDxmph0DFZrPWQH64WIrMm+yxNLmNZ/T1n uyiLUgDnhDRsCDVk3LWyvGc6WNspXeWMB47UgJKA30Vtvm4ZA3B8rOTPwhZ7L+hrm0us fs8A== X-Gm-Message-State: ALoCoQlzaxqCiAUopPGoEY0sPXIU6Kh+mAtGX+A87ZBdiSmiTuipqdQ6F7ul/QgIoWmba6QT1de7 MIME-Version: 1.0 X-Received: by 10.50.126.33 with SMTP id mv1mr11278145igb.27.1428493086613; Wed, 08 Apr 2015 04:38:06 -0700 (PDT) Received: by 10.36.54.67 with HTTP; Wed, 8 Apr 2015 04:38:06 -0700 (PDT) In-Reply-To: <20150402203235.GB10627@tatooine> References: <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> <20150402201851.GA10627@tatooine> <20150402203235.GB10627@tatooine> Date: Wed, 8 Apr 2015 13:38:06 +0200 Message-ID: From: Magnus Therning To: David Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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 2 April 2015 at 22:32, Magnus Therning wrote: > On Thu, Apr 02, 2015 at 09:20:42PM +0100, David Scott wrote: >> On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning wrote: >> > Hmm, I'm now wondering if I've done something completely wrong here. >> > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I >> > also get absolutely nothing in reply on HTTP requests... that wasn't >> > exactly what I expected. I did expect a reply with a bit of HTML. >> > >> > ~~~ output on xen console on ARM >> > Sending DHCP broadcast (length 552) >> > DHCP response: >> > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 >> > siaddr 192.168.0.1 giaddr 0.0.0.0 >> > chaddr 00163e2128a900000000000000000000 sname file >> > DHCP: offer received: 192.168.0.27 >> > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS >> > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Server >> > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400) >> > Sending DHCP broadcast (length 552) >> > DHCP response: >> > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 >> > siaddr 192.168.0.1 giaddr 0.0.0.0 >> > chaddr 00163e2128a900000000000000000000 sname file >> > DHCP: offer received >> > IPv4: 192.168.0.27 >> > Netmask: 255.255.255.0 >> > Gateways: >> > [192.168.0.1] >> > sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false >> > ARP: sending gratuitous from 192.168.0.27 >> > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw >> > [192.168.0.1] >> > Manager: configuration done >> > ARP responding to: who-has 192.168.0.27? >> > ARP: transmitting probe -> 192.168.0.11 >> > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd >> > conn 1 closed >> > conn 2 closed >> > ARP responding to: who-has 192.168.0.27? >> > conn 3 closed >> > conn 4 closed >> > ~~~ >> > >> > ~~~ on my laptop >> > % curl http://192.168.0.27/ >> > ~~~ >> > >> > curl doesn't produce any output, but shortly after invoking it I see a >> > `conn N closed` on teh Xen console. >> > >> >> Could you grab a tcpdump of that and post the .pcap file? > > I've attached it, and put it on my Dropbox just in case the list > doesn't like attachments. > > https://www.dropbox.com/s/u0zoeciy6t30sjz/arm-xen-www.pcap?dl=0 > > It's captured using `tcpdump -w arm-xen-www.pcap host 192.168.0.27`. > Let me know you need me to re-capture with some other switches on. Anyone with any pointers on where I should start looking for this issue on my own? Any test suites I can run that might help me locate where in the stack the issue is? Or maybe there's a known good version I can revert to just in order to verify that there's nothing more seriously wrong with my setup? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus _______________________________________________ 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 Apr 08 11:38:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Apr 2015 11:38:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfoJ8-0006h0-8l; Wed, 08 Apr 2015 11:38:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfoJ7-0006gr-6u for mirageos-devel@lists.xenproject.org; Wed, 08 Apr 2015 11:38:09 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id CA/B4-02119-02315255; Wed, 08 Apr 2015 11:38:08 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1428493086!10286552!1 X-Originating-IP: [209.85.213.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25543 invoked from network); 8 Apr 2015 11:38:07 -0000 Received: from mail-ig0-f178.google.com (HELO mail-ig0-f178.google.com) (209.85.213.178) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 8 Apr 2015 11:38:07 -0000 Received: by iget9 with SMTP id t9so27451999ige.1 for ; Wed, 08 Apr 2015 04:38:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4mRWVKjDNpJ/x2tphhGWwbwbr7Sfj1dWuZdCkPUoTZg=; b=C0EwUjKjn1R2I2An8K7Rfr0zBCCWh1rMGho6C6wCKJtTb4KnqjxsRpwv9HUKJgtkK5 eY4SqMZFNxg3vAGBevk76CLpoATfvgrTmijpDc5KjR74LE1o1hPMkAgzJ2ZVuUf9GM9W XbSI1JAWe+I5/3cMAH1A10O7fuUDGJ75EiLgnrDJRKy281VzelYHZ96bU3YmgIpQ2oXk niViwJ1KKH2+N1KbeLAOAOXpP4AipVdeS5iDxmph0DFZrPWQH64WIrMm+yxNLmNZ/T1n uyiLUgDnhDRsCDVk3LWyvGc6WNspXeWMB47UgJKA30Vtvm4ZA3B8rOTPwhZ7L+hrm0us fs8A== X-Gm-Message-State: ALoCoQlzaxqCiAUopPGoEY0sPXIU6Kh+mAtGX+A87ZBdiSmiTuipqdQ6F7ul/QgIoWmba6QT1de7 MIME-Version: 1.0 X-Received: by 10.50.126.33 with SMTP id mv1mr11278145igb.27.1428493086613; Wed, 08 Apr 2015 04:38:06 -0700 (PDT) Received: by 10.36.54.67 with HTTP; Wed, 8 Apr 2015 04:38:06 -0700 (PDT) In-Reply-To: <20150402203235.GB10627@tatooine> References: <20150329185230.GA7522@tatooine> <20150330211137.GA2701@tatooine> <6F46F15C-1100-482E-B74E-16C177E88F31@recoil.org> <166C00D9-5A83-4FBC-B0C0-BCB13A37B3A5@recoil.org> <20150402201851.GA10627@tatooine> <20150402203235.GB10627@tatooine> Date: Wed, 8 Apr 2015 13:38:06 +0200 Message-ID: From: Magnus Therning To: David Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-www on xen and networking (on ARM) 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 2 April 2015 at 22:32, Magnus Therning wrote: > On Thu, Apr 02, 2015 at 09:20:42PM +0100, David Scott wrote: >> On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning wrote: >> > Hmm, I'm now wondering if I've done something completely wrong here. >> > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I >> > also get absolutely nothing in reply on HTTP requests... that wasn't >> > exactly what I expected. I did expect a reply with a bit of HTML. >> > >> > ~~~ output on xen console on ARM >> > Sending DHCP broadcast (length 552) >> > DHCP response: >> > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 >> > siaddr 192.168.0.1 giaddr 0.0.0.0 >> > chaddr 00163e2128a900000000000000000000 sname file >> > DHCP: offer received: 192.168.0.27 >> > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS >> > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Server >> > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400) >> > Sending DHCP broadcast (length 552) >> > DHCP response: >> > input ciaddr 0.0.0.0 yiaddr 192.168.0.27 >> > siaddr 192.168.0.1 giaddr 0.0.0.0 >> > chaddr 00163e2128a900000000000000000000 sname file >> > DHCP: offer received >> > IPv4: 192.168.0.27 >> > Netmask: 255.255.255.0 >> > Gateways: >> > [192.168.0.1] >> > sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false >> > ARP: sending gratuitous from 192.168.0.27 >> > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw >> > [192.168.0.1] >> > Manager: configuration done >> > ARP responding to: who-has 192.168.0.27? >> > ARP: transmitting probe -> 192.168.0.11 >> > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd >> > conn 1 closed >> > conn 2 closed >> > ARP responding to: who-has 192.168.0.27? >> > conn 3 closed >> > conn 4 closed >> > ~~~ >> > >> > ~~~ on my laptop >> > % curl http://192.168.0.27/ >> > ~~~ >> > >> > curl doesn't produce any output, but shortly after invoking it I see a >> > `conn N closed` on teh Xen console. >> > >> >> Could you grab a tcpdump of that and post the .pcap file? > > I've attached it, and put it on my Dropbox just in case the list > doesn't like attachments. > > https://www.dropbox.com/s/u0zoeciy6t30sjz/arm-xen-www.pcap?dl=0 > > It's captured using `tcpdump -w arm-xen-www.pcap host 192.168.0.27`. > Let me know you need me to re-capture with some other switches on. Anyone with any pointers on where I should start looking for this issue on my own? Any test suites I can run that might help me locate where in the stack the issue is? Or maybe there's a known good version I can revert to just in order to verify that there's nothing more seriously wrong with my setup? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus _______________________________________________ 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 Apr 08 14:13:24 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Apr 2015 14:13: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 1YfqjH-0004Ay-Ez; Wed, 08 Apr 2015 14:13:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfqjG-0004At-4e for mirageos-devel@lists.xenproject.org; Wed, 08 Apr 2015 14:13:18 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 03/9D-02119-D7735255; Wed, 08 Apr 2015 14:13:17 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-5.tower-206.messagelabs.com!1428502394!14445090!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.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13073 invoked from network); 8 Apr 2015 14:13:14 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Apr 2015 14:13:14 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [62.49.66.12] (port=52742 helo=[192.168.15.7]) 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 1YfqjC-0007dp-h9 (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 08 Apr 2015 15:13:14 +0100 From: Amir Chaudhry Message-Id: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> Date: Wed, 8 Apr 2015 15:13:15 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - **Thursday** 9th at 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place on **Thursday** afternoon 4pm GMT. Pl= ease note the change of day for this call! We'll be using Google Hangout again and I'll circulate the link shortly be= fore the call -- both to this list and in the IRC channel, #mirage on freen= ode -- (hint: it'll be the same link as last time). The agenda for this week is currently as follows: =95 Quality and Test =95 Irmin update If you have things to add/edit, please do so at https://github.com/mirage/m= irage-www/wiki/Call-Agenda Join us at 4pm GMT on Thursday! Best wishes, 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 Apr 08 14:13:24 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Apr 2015 14:13: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 1YfqjH-0004Ay-Ez; Wed, 08 Apr 2015 14:13:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfqjG-0004At-4e for mirageos-devel@lists.xenproject.org; Wed, 08 Apr 2015 14:13:18 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 03/9D-02119-D7735255; Wed, 08 Apr 2015 14:13:17 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-5.tower-206.messagelabs.com!1428502394!14445090!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.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13073 invoked from network); 8 Apr 2015 14:13:14 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Apr 2015 14:13:14 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [62.49.66.12] (port=52742 helo=[192.168.15.7]) 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 1YfqjC-0007dp-h9 (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 08 Apr 2015 15:13:14 +0100 From: Amir Chaudhry Message-Id: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> Date: Wed, 8 Apr 2015 15:13:15 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - **Thursday** 9th at 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place on **Thursday** afternoon 4pm GMT. Pl= ease note the change of day for this call! We'll be using Google Hangout again and I'll circulate the link shortly be= fore the call -- both to this list and in the IRC channel, #mirage on freen= ode -- (hint: it'll be the same link as last time). The agenda for this week is currently as follows: =95 Quality and Test =95 Irmin update If you have things to add/edit, please do so at https://github.com/mirage/m= irage-www/wiki/Call-Agenda Join us at 4pm GMT on Thursday! Best wishes, 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 Apr 08 16:05:01 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Apr 2015 16:05: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 1YfsTH-00009x-Mb; Wed, 08 Apr 2015 16:04:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YfsTG-00009s-3s for mirageos-devel@lists.xenproject.org; Wed, 08 Apr 2015 16:04:54 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id BB/01-16511-5A155255; Wed, 08 Apr 2015 16:04:53 +0000 X-Env-Sender: rudi.grinberg@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1428509091!16470903!1 X-Originating-IP: [209.85.223.179] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4518 invoked from network); 8 Apr 2015 16:04:52 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Apr 2015 16:04:52 -0000 Received: by iebmp1 with SMTP id mp1so78240913ieb.0 for ; Wed, 08 Apr 2015 09:04:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version:content-type; bh=UXzMzqJYzSb/W+42PxoAxmF3AcD9YEbPxqQ/p151TYQ=; b=EMYauX2YYaZfNzheIBQg9N9NNuoXGaYNauvw1OJZ976kI5zJuPO5Je7heM4bVeWYZu ayrHCL+W4hqbx9L2rL3HWK6lld6OlNzLkPTQO2asYghkwMnoQniJDv9H/2iUlSY11jX1 c9ofwXQf3IxEGQXTBuTTrHXvtDWRSLivyky2wtSgVATgk875tKvG/ZHQd2MtN3Zmp0UJ iguQWYrMIxvidiZCV6QnByaSgJb9wePjFQss3rw+addKy/h8q/hfY8Y2TvfIzQsHD4lG CyAl8ht4jwsiHyYQ5huhRvxVfahh4BYcuzYFvnnOjZFy1wqQjThkvuFTtlpWAp3YNBq6 VK4Q== X-Received: by 10.50.90.179 with SMTP id bx19mr13132842igb.43.1428509090802; Wed, 08 Apr 2015 09:04:50 -0700 (PDT) Received: from Rudis-MacBook-Pro.local (dsl-69-171-144-193.acanac.net. [69.171.144.193]) by mx.google.com with ESMTPSA id qs3sm7040292igb.8.2015.04.08.09.04.50 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Apr 2015 09:04:50 -0700 (PDT) Date: Wed, 8 Apr 2015 12:08:54 -0400 From: Rudi Grinberg To: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Message-ID: X-Mailer: Airmail Beta (298) MIME-Version: 1.0 Subject: [MirageOS-devel] What was the reasoning for splitting out mirage-http? 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="===============8707703128224435919==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8707703128224435919== Content-Type: multipart/alternative; boundary="55255296_2443a858_131" --55255296_2443a858_131 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, Back in 2013, mirage-http was extracted out of cohttp into it=E2=80=99s o= wn repository. Although I=E2=80=99m ignorant of how the decision was made= , I understand that there could have been good reasons for this a couple = of years ago. Today, however, it seems like there=E2=80=99s less good rea= sons for such a split. Now that opam supports multiple packages out of th= e same repo and since we=E2=80=99re planning on releasing cohttp backends= as their own packages =5B1=5D, maybe it makes sense to treat mirage-http= the same way=3F The reason why I=E2=80=99m bringing this up now is that the current situa= tion does have the disadvantage of confusing users and creating possibly = unnecessary churn for maintainers =5B2=5D Thanks, Rudi. =5B1=5D=C2=A0https://github.com/mirage/ocaml-cohttp/issues/238 =5B2=5D=C2=A0https://github.com/mirage/mirage/issues/301=23issuecomment-9= 0729110 --55255296_2443a858_131 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline = = --Apple-Mail=_FFFF0F5F-CE73-408C-B4E8-E7696D7E8D1A-- --===============2022432587026760340== 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 --===============2022432587026760340==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 08 16:53:00 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Apr 2015 16:53: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 1YftDm-0005q9-2Z; Wed, 08 Apr 2015 16:52:58 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YftDk-0005q4-7x for mirageos-devel@lists.xenproject.org; Wed, 08 Apr 2015 16:52:56 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id A5/6B-09816-7EC55255; Wed, 08 Apr 2015 16:52:55 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1428511972!16440514!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7535 invoked from network); 8 Apr 2015 16:52:52 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Apr 2015 16:52:52 -0000 Received: by wgyo15 with SMTP id o15so83783736wgy.2 for ; Wed, 08 Apr 2015 09:52:51 -0700 (PDT) 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 :message-id:references:to; bh=fgbUQZVgyrqxZnBASvUqcZ6HQSCNvIqTINyyEuGuN+E=; b=A78GXl+68eD9vfn/vOs7E8va6idtgJYeHvHqjU+lEnWmaW0U+0IjNz7jPOetXTLXb6 5UZDWVrXnLkrjrAPS2k1X0ux9b85A5MCl8O+XNjZXIYJsv/8AefnorqmenAnlRQKZ+F9 DAYe2FBBysTPGwul9iqRuj6wygiSAXWMHd7C2K+5IqgPpXMG7yQuhUkTcLJXw7lM0+zm qz52iPZo06rHtYCirn3NYM35tuBfQGccwa1KMN+YR1Slr9sVMtPgBdKOjtFurEtB1qne 0WbUBB6prrb/k/EwGZwxcN9oX69vC44cmkt+563X4jzsyxkWdgVJ2nhEp6Bb5OEmw5+P lHjQ== X-Received: by 10.194.171.136 with SMTP id au8mr52682449wjc.6.1428511971793; Wed, 08 Apr 2015 09:52:51 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id w5sm16453439wiz.11.2015.04.08.09.52.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Apr 2015 09:52:50 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 8 Apr 2015 18:52:49 +0200 Message-Id: <5F30557E-1C79-4F20-86AA-6BD25D692F2E@gazagnaire.org> References: To: Rudi Grinberg X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] What was the reasoning for splitting out mirage-http? 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="===============2022432587026760340==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2022432587026760340== Content-Type: multipart/alternative; boundary="Apple-Mail=_FFFF0F5F-CE73-408C-B4E8-E7696D7E8D1A" --Apple-Mail=_FFFF0F5F-CE73-408C-B4E8-E7696D7E8D1A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Back in 2013, mirage-http was extracted out of cohttp into it=E2=80=99s = own repository. Although I=E2=80=99m ignorant of how the decision was = made, I understand that there could have been good reasons for this a = couple of years ago. Today, however, it seems like there=E2=80=99s less = good reasons for such a split. Now that opam supports multiple packages = out of the same repo and since we=E2=80=99re planning on releasing = cohttp backends as their own packages [1], maybe it makes sense to treat = mirage-http the same way? Yes, we wanted to have a separate opam package for mirage-http, and at = the time it was the only possible option (now, with .opam, it = would be possible to keep the code in the same repository). However I think having the code outside in this case is better (even = though not necessary easier) as we also need to synchronise the release = of mirage-http with the mirage tool (which generates some code using = mirage-http). So I think, having a separate release schedule for cohttp = and mirage-cohttp (and thus separate repositories and maintainers) makes = sense in that case even if it can cause some trouble to the maintainers. Best, Thomas >=20 > The reason why I=E2=80=99m bringing this up now is that the current = situation does have the disadvantage of confusing users and creating = possibly unnecessary churn for maintainers [2] >=20 >=20 > Thanks, >=20 > Rudi. >=20 > [1] https://github.com/mirage/ocaml-cohttp/issues/238 = > [2] https://github.com/mirage/mirage/issues/301#issuecomment-90729110 = _______= ________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_FFFF0F5F-CE73-408C-B4E8-E7696D7E8D1A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Back in 2013, mirage-http was = extracted out of cohttp into it=E2=80=99s own repository. Although I=E2=80= =99m ignorant of how the decision was made, I understand that there = could have been good reasons for this a couple of years ago. Today, = however, it seems like there=E2=80=99s less good reasons for such a = split. Now that opam supports multiple packages out of the same repo and = since we=E2=80=99re planning on releasing cohttp backends as their own = packages [1], maybe it makes sense to treat mirage-http the same = way?

Yes, = we wanted to have a separate opam package for mirage-http, and at the = time it was the only possible option (now, with <package>.opam, it = would be possible to keep the code in the same = repository).

However I think having = the code outside in this case is better (even though not necessary = easier) as we also need to synchronise the release of mirage-http with = the mirage tool (which generates some code using mirage-http). So I = think, having a separate release schedule for cohttp and mirage-cohttp = (and thus separate repositories and maintainers) makes sense in that = case even if it can cause some trouble to the maintainers.

Best,
Thomas


The reason why I=E2=80=99m = bringing this up now is that the current situation does have the = disadvantage of confusing users and creating possibly unnecessary churn = for maintainers [2]


Thanks,

Rudi.
[2] https://github.com/mirage/mirage/issues/301#issuecomment-907291= 10
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel

= = --Apple-Mail=_FFFF0F5F-CE73-408C-B4E8-E7696D7E8D1A-- --===============2022432587026760340== 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 --===============2022432587026760340==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 09 11:21:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 11:21:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgAWn-0000OR-PY; Thu, 09 Apr 2015 11:21:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgAWn-0000OI-32 for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 11:21:45 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id 91/34-12190-8C066255; Thu, 09 Apr 2015 11:21:44 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-10.tower-206.messagelabs.com!1428578503!9403315!1 X-Originating-IP: [131.111.8.143] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25601 invoked from network); 9 Apr 2015 11:21:43 -0000 Received: from ppsw-43.csi.cam.ac.uk (HELO ppsw-43.csi.cam.ac.uk) (131.111.8.143) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 11:21:43 -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]:55073 helo=[192.168.0.35]) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YgAWl-00069B-nM (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 09 Apr 2015 12:21:43 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> Date: Thu, 9 Apr 2015 12:21:45 +0100 Message-Id: <7E69DFBA-26B4-4456-84D1-AA9EE49AED63@cam.ac.uk> References: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - **Thursday** 9th at 4pm BST 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, Someone just reminded me that the clocks changed recently in the UK and we'= re now on British Summer Time (BST), which is GMT+1. The call will be today is at 4pm BST (not GMT). To avoid further confusion = below are local times for a few different locations. Europe (Norway, France, Croatia) - 5pm CEST East coast USA (New York) - 11am EDT West coast USA (San Francisco) - 8am PDT Apologies if this causes any issues. Amir On 8 Apr 2015, at 15:13, Amir Chaudhry wrote: > Hi folks, > = > The next Mirage call will take place on **Thursday** afternoon 4pm GMT. = Please note the change of day for this call! > = > We'll be using Google Hangout again and I'll circulate the link shortly = before the call -- both to this list and in the IRC channel, #mirage on fre= enode -- (hint: it'll be the same link as last time). > = > The agenda for this week is currently as follows: > = > =95 Quality and Test > =95 Irmin update > = > If you have things to add/edit, please do so at https://github.com/mirage= /mirage-www/wiki/Call-Agenda > = > Join us at 4pm GMT on Thursday! > = > Best wishes, > 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 Thu Apr 09 11:21:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 11:21:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgAWn-0000OR-PY; Thu, 09 Apr 2015 11:21:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgAWn-0000OI-32 for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 11:21:45 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id 91/34-12190-8C066255; Thu, 09 Apr 2015 11:21:44 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-10.tower-206.messagelabs.com!1428578503!9403315!1 X-Originating-IP: [131.111.8.143] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25601 invoked from network); 9 Apr 2015 11:21:43 -0000 Received: from ppsw-43.csi.cam.ac.uk (HELO ppsw-43.csi.cam.ac.uk) (131.111.8.143) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 11:21:43 -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]:55073 helo=[192.168.0.35]) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YgAWl-00069B-nM (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 09 Apr 2015 12:21:43 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> Date: Thu, 9 Apr 2015 12:21:45 +0100 Message-Id: <7E69DFBA-26B4-4456-84D1-AA9EE49AED63@cam.ac.uk> References: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - **Thursday** 9th at 4pm BST 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, Someone just reminded me that the clocks changed recently in the UK and we'= re now on British Summer Time (BST), which is GMT+1. The call will be today is at 4pm BST (not GMT). To avoid further confusion = below are local times for a few different locations. Europe (Norway, France, Croatia) - 5pm CEST East coast USA (New York) - 11am EDT West coast USA (San Francisco) - 8am PDT Apologies if this causes any issues. Amir On 8 Apr 2015, at 15:13, Amir Chaudhry wrote: > Hi folks, > = > The next Mirage call will take place on **Thursday** afternoon 4pm GMT. = Please note the change of day for this call! > = > We'll be using Google Hangout again and I'll circulate the link shortly = before the call -- both to this list and in the IRC channel, #mirage on fre= enode -- (hint: it'll be the same link as last time). > = > The agenda for this week is currently as follows: > = > =95 Quality and Test > =95 Irmin update > = > If you have things to add/edit, please do so at https://github.com/mirage= /mirage-www/wiki/Call-Agenda > = > Join us at 4pm GMT on Thursday! > = > Best wishes, > 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 Thu Apr 09 15:00:25 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 15:00: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 1YgDwM-00066j-1j; Thu, 09 Apr 2015 15:00:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgDwL-00066e-08 for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 15:00:21 +0000 Received: from [193.109.254.147] by server-2.bemta-14.messagelabs.com id 4C/4C-14319-40496255; Thu, 09 Apr 2015 15:00:20 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-3.tower-27.messagelabs.com!1428591619!13357718!1 X-Originating-IP: [131.111.8.133] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11475 invoked from network); 9 Apr 2015 15:00:19 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 15:00:19 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [62.49.66.12] (port=56201 helo=[192.168.15.7]) 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 1YgDwJ-0005Bk-gI (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 09 Apr 2015 16:00:19 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <7E69DFBA-26B4-4456-84D1-AA9EE49AED63@cam.ac.uk> Date: Thu, 9 Apr 2015 16:00:21 +0100 Message-Id: <58F2D9FA-17D0-4A2F-942D-981340B04BDF@cam.ac.uk> References: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> <7E69DFBA-26B4-4456-84D1-AA9EE49AED63@cam.ac.uk> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - **Thursday** 9th at 4pm BST 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, the Hangout link is: https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya AC On 9 Apr 2015, at 12:21, Amir Chaudhry wrote: > Hi folks, > = > Someone just reminded me that the clocks changed recently in the UK and w= e're now on British Summer Time (BST), which is GMT+1. > = > The call will be today is at 4pm BST (not GMT). To avoid further confusio= n below are local times for a few different locations. > = > Europe (Norway, France, Croatia) - 5pm CEST > East coast USA (New York) - 11am EDT > West coast USA (San Francisco) - 8am PDT > = > Apologies if this causes any issues. > = > Amir > = > On 8 Apr 2015, at 15:13, Amir Chaudhry wrote: > = >> Hi folks, >> = >> The next Mirage call will take place on **Thursday** afternoon 4pm GMT. = Please note the change of day for this call! >> = >> We'll be using Google Hangout again and I'll circulate the link shortly= before the call -- both to this list and in the IRC channel, #mirage on fr= eenode -- (hint: it'll be the same link as last time). >> = >> The agenda for this week is currently as follows: >> = >> =95 Quality and Test >> =95 Irmin update >> = >> If you have things to add/edit, please do so at https://github.com/mirag= e/mirage-www/wiki/Call-Agenda >> = >> Join us at 4pm GMT on Thursday! >> = >> Best wishes, >> Amir > = > = > _______________________________________________ > 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 Thu Apr 09 15:00:25 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 15:00: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 1YgDwM-00066j-1j; Thu, 09 Apr 2015 15:00:22 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgDwL-00066e-08 for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 15:00:21 +0000 Received: from [193.109.254.147] by server-2.bemta-14.messagelabs.com id 4C/4C-14319-40496255; Thu, 09 Apr 2015 15:00:20 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-3.tower-27.messagelabs.com!1428591619!13357718!1 X-Originating-IP: [131.111.8.133] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11475 invoked from network); 9 Apr 2015 15:00:19 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 15:00:19 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [62.49.66.12] (port=56201 helo=[192.168.15.7]) 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 1YgDwJ-0005Bk-gI (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 09 Apr 2015 16:00:19 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <7E69DFBA-26B4-4456-84D1-AA9EE49AED63@cam.ac.uk> Date: Thu, 9 Apr 2015 16:00:21 +0100 Message-Id: <58F2D9FA-17D0-4A2F-942D-981340B04BDF@cam.ac.uk> References: <558D7E35-A8CA-4611-ABBA-06013E927A9B@cam.ac.uk> <7E69DFBA-26B4-4456-84D1-AA9EE49AED63@cam.ac.uk> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - **Thursday** 9th at 4pm BST 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, the Hangout link is: https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya AC On 9 Apr 2015, at 12:21, Amir Chaudhry wrote: > Hi folks, > = > Someone just reminded me that the clocks changed recently in the UK and w= e're now on British Summer Time (BST), which is GMT+1. > = > The call will be today is at 4pm BST (not GMT). To avoid further confusio= n below are local times for a few different locations. > = > Europe (Norway, France, Croatia) - 5pm CEST > East coast USA (New York) - 11am EDT > West coast USA (San Francisco) - 8am PDT > = > Apologies if this causes any issues. > = > Amir > = > On 8 Apr 2015, at 15:13, Amir Chaudhry wrote: > = >> Hi folks, >> = >> The next Mirage call will take place on **Thursday** afternoon 4pm GMT. = Please note the change of day for this call! >> = >> We'll be using Google Hangout again and I'll circulate the link shortly= before the call -- both to this list and in the IRC channel, #mirage on fr= eenode -- (hint: it'll be the same link as last time). >> = >> The agenda for this week is currently as follows: >> = >> =95 Quality and Test >> =95 Irmin update >> = >> If you have things to add/edit, please do so at https://github.com/mirag= e/mirage-www/wiki/Call-Agenda >> = >> Join us at 4pm GMT on Thursday! >> = >> Best wishes, >> Amir > = > = > _______________________________________________ > 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 Thu Apr 09 17:22:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 17:22: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 1YgG9w-0004XK-Gq; Thu, 09 Apr 2015 17:22:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgG9v-0004WP-LS for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 17:22:31 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id 57/D3-14975-655B6255; Thu, 09 Apr 2015 17:22:30 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1428600149!15062848!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4826 invoked from network); 9 Apr 2015 17:22:29 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 17:22:29 -0000 Received: by wgyo15 with SMTP id o15so116641237wgy.2 for ; Thu, 09 Apr 2015 10:22:29 -0700 (PDT) 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=s+W7DTCbbfxvrO1CTeKRGF14WwogoEBvkyyqPS6Y2j0=; b=yRwR6E1xtes7m+kz9SHieRdskSQgiAaMurudbkZUH00OeAsauaSL0PFh2L4BB9Mdn1 3pus9k50UpFfaviG2F1ST8zmf6i4bNPithaRCPX44rXJpD56UjteZMWyUFaLHNi+LWw3 wq5lwhexbNtJonD+TRgVqcMlLdFMXvAkIbax2GDBWhXeGmp61lLfCsF/1jRcuSr/rwz+ iR12mlHhq1CfnCFarVzl9BhCXRyfUBMFZ47ZzgMryebmt5emyv5+EfvSSTtcVDCPiGEp yxc0LIAZgn2XY3XpGP1eNmkYq9+k1/9lLXYN4RdPwduztdQsZuMFs3OyBDhzVDp7fqUd z6Kw== X-Received: by 10.194.177.195 with SMTP id cs3mr60819848wjc.141.1428600149296; Thu, 09 Apr 2015 10:22:29 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id g5sm20968924wjr.19.2015.04.09.10.22.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 10:22:28 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 9 Apr 2015 19:22:26 +0200 Message-Id: <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 >>> BC.make_head : >>> Irmin.config -> ('a -> Irmin.task) -> parents:head list -> >>> msg:'a -> View.t -> ('a -> t) Lwt.t Do you really need a View.t here? How do you build that value? Do you first take a view from somewhere and then tweak it to get the value you want for the merge? Or you just run a sequence of updates? I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? Thomas >>> >>> to implement CueKeeper's API: >>> >>> module Commit : sig >>> type t >>> val commit : >>> parents:t list -> >>> Staging.t -> >>> msg:string -> >>> t Lwt.t >>> >>> How can I take two commits, generate a view (manually) with the >>> results of my custom merge, and then add the result as a new commit >>> with both of the original parents? >> >> Something like: >> >> let commit ~parents staging ~msg = >> match staging.Staging.commit with >> | None -> assert false >> | Some t -> >> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> >> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; >> V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> >> {t with c_store = tmp_branch} > > It doesn't seem to work. I tested with this code (on my "test_merging" branch): > > https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d > > Git.Commit.checkout base >>= fun stage -> > Git.Staging.update stage ["foo"] "a" >>= fun () -> > Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> > Git.Staging.update stage ["foo"] "b" >>= fun () -> > Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> > Git.Staging.update stage ["foo"] "merged" >>= fun () -> > Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> > Git.Branch.fast_forward_to master result >>= function > > For testing, it uses the Git backend with the directory "test_db". > Looking at the result with gitk, I have an initial commit containing > "orig" with a direct child "Merge" containing "merged". > > [ I also had to expose "VIEW.head = S.head" in Irmin: > https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 > and I modified your code slightly to make "parents" optional and to be > a Commit.t, but that shouldn't make any difference I think. ] > >> I'll see if I can add your `make_head` function. >> >> Thomas >> >>> >>>>> Currently, I merge to create a new commit, test it, and then do a >>>>> fast-forward to update the branch to include the merge if the test >>>>> passes. But if I can use custom merge code, then it would be OK to >>>>> merge directly to the branch when my merge code returns, since it will >>>>> already have had a chance to test it. >>>> >>>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >>> >>> Thanks! [ As noted elsewhere, it would be useful to distinguish the >>> case where it's already up-to-date (success; no futher action needed) >>> from the case where it's not an ancestor (failure; retry merge with >>> new head). ] >>> >>>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>>> >>>> Best, >>>> Thomas >>>> >>> >>> >>> >>> -- >>> Dr Thomas Leonard http://0install.net/ >>> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >>> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 09 17:22:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 17:22: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 1YgG9w-0004XK-Gq; Thu, 09 Apr 2015 17:22:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgG9v-0004WP-LS for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 17:22:31 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id 57/D3-14975-655B6255; Thu, 09 Apr 2015 17:22:30 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1428600149!15062848!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4826 invoked from network); 9 Apr 2015 17:22:29 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 17:22:29 -0000 Received: by wgyo15 with SMTP id o15so116641237wgy.2 for ; Thu, 09 Apr 2015 10:22:29 -0700 (PDT) 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=s+W7DTCbbfxvrO1CTeKRGF14WwogoEBvkyyqPS6Y2j0=; b=yRwR6E1xtes7m+kz9SHieRdskSQgiAaMurudbkZUH00OeAsauaSL0PFh2L4BB9Mdn1 3pus9k50UpFfaviG2F1ST8zmf6i4bNPithaRCPX44rXJpD56UjteZMWyUFaLHNi+LWw3 wq5lwhexbNtJonD+TRgVqcMlLdFMXvAkIbax2GDBWhXeGmp61lLfCsF/1jRcuSr/rwz+ iR12mlHhq1CfnCFarVzl9BhCXRyfUBMFZ47ZzgMryebmt5emyv5+EfvSSTtcVDCPiGEp yxc0LIAZgn2XY3XpGP1eNmkYq9+k1/9lLXYN4RdPwduztdQsZuMFs3OyBDhzVDp7fqUd z6Kw== X-Received: by 10.194.177.195 with SMTP id cs3mr60819848wjc.141.1428600149296; Thu, 09 Apr 2015 10:22:29 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id g5sm20968924wjr.19.2015.04.09.10.22.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 10:22:28 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 9 Apr 2015 19:22:26 +0200 Message-Id: <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 >>> BC.make_head : >>> Irmin.config -> ('a -> Irmin.task) -> parents:head list -> >>> msg:'a -> View.t -> ('a -> t) Lwt.t Do you really need a View.t here? How do you build that value? Do you first take a view from somewhere and then tweak it to get the value you want for the merge? Or you just run a sequence of updates? I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? Thomas >>> >>> to implement CueKeeper's API: >>> >>> module Commit : sig >>> type t >>> val commit : >>> parents:t list -> >>> Staging.t -> >>> msg:string -> >>> t Lwt.t >>> >>> How can I take two commits, generate a view (manually) with the >>> results of my custom merge, and then add the result as a new commit >>> with both of the original parents? >> >> Something like: >> >> let commit ~parents staging ~msg = >> match staging.Staging.commit with >> | None -> assert false >> | Some t -> >> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> >> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; >> V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> >> {t with c_store = tmp_branch} > > It doesn't seem to work. I tested with this code (on my "test_merging" branch): > > https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d > > Git.Commit.checkout base >>= fun stage -> > Git.Staging.update stage ["foo"] "a" >>= fun () -> > Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> > Git.Staging.update stage ["foo"] "b" >>= fun () -> > Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> > Git.Staging.update stage ["foo"] "merged" >>= fun () -> > Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> > Git.Branch.fast_forward_to master result >>= function > > For testing, it uses the Git backend with the directory "test_db". > Looking at the result with gitk, I have an initial commit containing > "orig" with a direct child "Merge" containing "merged". > > [ I also had to expose "VIEW.head = S.head" in Irmin: > https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 > and I modified your code slightly to make "parents" optional and to be > a Commit.t, but that shouldn't make any difference I think. ] > >> I'll see if I can add your `make_head` function. >> >> Thomas >> >>> >>>>> Currently, I merge to create a new commit, test it, and then do a >>>>> fast-forward to update the branch to include the merge if the test >>>>> passes. But if I can use custom merge code, then it would be OK to >>>>> merge directly to the branch when my merge code returns, since it will >>>>> already have had a chance to test it. >>>> >>>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >>> >>> Thanks! [ As noted elsewhere, it would be useful to distinguish the >>> case where it's already up-to-date (success; no futher action needed) >>> from the case where it's not an ancestor (failure; retry merge with >>> new head). ] >>> >>>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>>> >>>> Best, >>>> Thomas >>>> >>> >>> >>> >>> -- >>> Dr Thomas Leonard http://0install.net/ >>> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >>> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 09 17:28:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 17:28:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgGFR-00054O-CZ; Thu, 09 Apr 2015 17:28:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgGFQ-00054H-IE for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 17:28:12 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id E0/49-11242-BA6B6255; Thu, 09 Apr 2015 17:28:11 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1428600491!15104255!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2155 invoked from network); 9 Apr 2015 17:28:11 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 17:28:11 -0000 Received: from mfilter6-d.gandi.net (mfilter6-d.gandi.net [217.70.178.135]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 0A059FB8B3 for ; Thu, 9 Apr 2015 19:28:11 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter6-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter6-d.gandi.net (mfilter6-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 7BdzymsLyDte for ; Thu, 9 Apr 2015 19:27:39 +0200 (CEST) X-Originating-IP: 131.111.184.18 Received: from [172.17.26.186] (global-1-18.nat.csx.cam.ac.uk [131.111.184.18]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 70620FB88B for ; Thu, 9 Apr 2015 19:27:39 +0200 (CEST) Message-ID: <5526B66C.2000601@somerandomidiot.com> Date: Thu, 09 Apr 2015 18:27:08 +0100 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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-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 folks, I've been working on a sort of ARP thing for the week or so which I've just put up publicly on GitHub: https://github.com/yomimono/irmin-arp It's an ARP implementation that uses an Irmin store wrapped around a Map to access and modify the cache, meaning that with each change you get history and a commit message. You can choose to use an in-memory Irmin store or you can use the Git-backed filesystem Irmin store interface; choosing a filesystem store means you can read back the store from another thread and make assertions about its state. With Magnus Skjegstad's mirage-vnetif software bridge and Thomas Gazagnaire's alcotest, I've used this to write tests attempting to verify reasonable (and documentation-compliant) behaviour of the implementation. Although I've currently disabled this, it's also possible to have the test history automatically committed to the repository (currently it will commit this to a subdirectory, test_results, which is not included in the overall code repo). For a quick demo, run `make test` and have a look in the `test_results` directory, where git repositories reflecting the changes in cache state for each test are reflected, e.g. showing the changes in the cache for a listening Arp.t when a speaker on the same software bridge sets four different IPs: ~/irmin-arp/test_results/input_changed_ip/listener$ git log --oneline 87fc498 entry added: 192.168.3.1 -> 02:50:2a:16:6d:01 6958e03 entry added: 10.20.254.2 -> 02:50:2a:16:6d:01 829df48 entry added: 10.50.20.22 -> 02:50:2a:16:6d:01 b903b4f entry added: 10.23.10.1 -> 02:50:2a:16:6d:01 fc34d1f Arp.create: Initial empty cache ... The overall repository in `test_results` has commits for test passes or failures, e.g.: ~/irmin-arp/test_results$ git log --oneline f978c35 merge_pairwise: remove_expired -> master 53c2c4b merge_pairwise: update expired f6106c1 merge_pairwise: remove expired 81ad78b merge_pairwise: original map 70d203f merge_conflicts_difft_noeds: test succeeded; removing data 70185f5 merge_conflicts_difft_nodes: expired_removed -> master 1195bff merge_conflicts_difft_nodes: remove expired entries 2618f4f merge_conflicts_difft_nodes: resolve arp entry 7bd9391 merge_conflicts_difft_nodes: set original map 067f38b merge_conflicts_difft_nodes: beginning new test ... I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. Thanks for your consideration and support. :) -Mindy _______________________________________________ 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 Apr 09 17:28:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 17:28:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgGFR-00054O-CZ; Thu, 09 Apr 2015 17:28:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgGFQ-00054H-IE for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 17:28:12 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id E0/49-11242-BA6B6255; Thu, 09 Apr 2015 17:28:11 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1428600491!15104255!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2155 invoked from network); 9 Apr 2015 17:28:11 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 17:28:11 -0000 Received: from mfilter6-d.gandi.net (mfilter6-d.gandi.net [217.70.178.135]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 0A059FB8B3 for ; Thu, 9 Apr 2015 19:28:11 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter6-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter6-d.gandi.net (mfilter6-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 7BdzymsLyDte for ; Thu, 9 Apr 2015 19:27:39 +0200 (CEST) X-Originating-IP: 131.111.184.18 Received: from [172.17.26.186] (global-1-18.nat.csx.cam.ac.uk [131.111.184.18]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 70620FB88B for ; Thu, 9 Apr 2015 19:27:39 +0200 (CEST) Message-ID: <5526B66C.2000601@somerandomidiot.com> Date: Thu, 09 Apr 2015 18:27:08 +0100 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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-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 folks, I've been working on a sort of ARP thing for the week or so which I've just put up publicly on GitHub: https://github.com/yomimono/irmin-arp It's an ARP implementation that uses an Irmin store wrapped around a Map to access and modify the cache, meaning that with each change you get history and a commit message. You can choose to use an in-memory Irmin store or you can use the Git-backed filesystem Irmin store interface; choosing a filesystem store means you can read back the store from another thread and make assertions about its state. With Magnus Skjegstad's mirage-vnetif software bridge and Thomas Gazagnaire's alcotest, I've used this to write tests attempting to verify reasonable (and documentation-compliant) behaviour of the implementation. Although I've currently disabled this, it's also possible to have the test history automatically committed to the repository (currently it will commit this to a subdirectory, test_results, which is not included in the overall code repo). For a quick demo, run `make test` and have a look in the `test_results` directory, where git repositories reflecting the changes in cache state for each test are reflected, e.g. showing the changes in the cache for a listening Arp.t when a speaker on the same software bridge sets four different IPs: ~/irmin-arp/test_results/input_changed_ip/listener$ git log --oneline 87fc498 entry added: 192.168.3.1 -> 02:50:2a:16:6d:01 6958e03 entry added: 10.20.254.2 -> 02:50:2a:16:6d:01 829df48 entry added: 10.50.20.22 -> 02:50:2a:16:6d:01 b903b4f entry added: 10.23.10.1 -> 02:50:2a:16:6d:01 fc34d1f Arp.create: Initial empty cache ... The overall repository in `test_results` has commits for test passes or failures, e.g.: ~/irmin-arp/test_results$ git log --oneline f978c35 merge_pairwise: remove_expired -> master 53c2c4b merge_pairwise: update expired f6106c1 merge_pairwise: remove expired 81ad78b merge_pairwise: original map 70d203f merge_conflicts_difft_noeds: test succeeded; removing data 70185f5 merge_conflicts_difft_nodes: expired_removed -> master 1195bff merge_conflicts_difft_nodes: remove expired entries 2618f4f merge_conflicts_difft_nodes: resolve arp entry 7bd9391 merge_conflicts_difft_nodes: set original map 067f38b merge_conflicts_difft_nodes: beginning new test ... I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. Thanks for your consideration and support. :) -Mindy _______________________________________________ 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 Apr 09 17:48:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 17:48: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 1YgGYc-0006wM-PQ; Thu, 09 Apr 2015 17:48:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgGYa-0006wB-UL for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 17:48:01 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id 73/EA-04861-F4BB6255; Thu, 09 Apr 2015 17:47:59 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1428601678!15079241!1 X-Originating-IP: [209.85.217.170] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5172 invoked from network); 9 Apr 2015 17:47:59 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 17:47:59 -0000 Received: by lbcga7 with SMTP id ga7so47285349lbc.1 for ; Thu, 09 Apr 2015 10:47:58 -0700 (PDT) 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=5uuGP8RSPlt2wWS6Gyt5hPjxHX4ZHZWfnGd8fgODGHA=; b=uYfZNGRDj4yvtZHZL8epWeShIPf8l9zL9txbqVC0wDpdzS+UtfUqwFRPuaqZRJAF+L F0w5CCruYJx2POGB1mDde4GG3E9I9dPsknISTzVyOzEuo1kkYW7dmnzWKo+/l53Hgggg BHXCZbTc9v3B2NkzUeIFcCO0h9NKiPfe3KaHQwUQV+T0bZLu8u6rBvQN17zJmlBqWFq/ Boco8i0AJB7pAnsJRrzyTMAqyXJOmAIsei/1OtinfCy9BTUy60lFKHdEp9yWIgHDZggy 2W2d+O+ECSuJi7SdlCI6cuU+XXQ3LTKxIdCW6twz2IUyXVNyG0y3ETJjAW9+xlUQpt3C L21A== MIME-Version: 1.0 X-Received: by 10.152.44.161 with SMTP id f1mr5420793lam.26.1428601678167; Thu, 09 Apr 2015 10:47:58 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Thu, 9 Apr 2015 10:47:58 -0700 (PDT) In-Reply-To: <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> Date: Thu, 9 Apr 2015 18:47:58 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 April 2015 at 18:22, Thomas Gazagnaire wrote: >>>> BC.make_head : >>>> Irmin.config -> ('a -> Irmin.task) -> parents:head list -> >>>> msg:'a -> View.t -> ('a -> t) Lwt.t > > > Do you really need a View.t here? How do you build that value? Do you first take a view from somewhere and then tweak it to get the value you want for the merge? Or you just run a sequence of updates? There are two cases. If the branch already contains a commit: 1. I use View.of_path to get the view. 2. I use BC.of_head to make a temporary branch. 3. I commit to the temporary branch with View.update_path. 4. After testing the commit, I use BC.compare_and_set_head to commit to the main branch. If the branch is empty: 1. I use View.empty to get the view. 2. I commit directly to the master branch with View.update_path (no testing is possible in this case). This works - it would just be a bit neater if there was a uniform way to make a commit from a view. > I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: > 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; > 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. > 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. > > I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? Sounds good to me. Thanks! > Thomas > > >>>> >>>> to implement CueKeeper's API: >>>> >>>> module Commit : sig >>>> type t >>>> val commit : >>>> parents:t list -> >>>> Staging.t -> >>>> msg:string -> >>>> t Lwt.t >>>> >>>> How can I take two commits, generate a view (manually) with the >>>> results of my custom merge, and then add the result as a new commit >>>> with both of the original parents? >>> >>> Something like: >>> >>> let commit ~parents staging ~msg = >>> match staging.Staging.commit with >>> | None -> assert false >>> | Some t -> >>> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> >>> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; >>> V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> >>> {t with c_store = tmp_branch} >> >> It doesn't seem to work. I tested with this code (on my "test_merging" branch): >> >> https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d >> >> Git.Commit.checkout base >>= fun stage -> >> Git.Staging.update stage ["foo"] "a" >>= fun () -> >> Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> >> Git.Staging.update stage ["foo"] "b" >>= fun () -> >> Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> >> Git.Staging.update stage ["foo"] "merged" >>= fun () -> >> Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> >> Git.Branch.fast_forward_to master result >>= function >> >> For testing, it uses the Git backend with the directory "test_db". >> Looking at the result with gitk, I have an initial commit containing >> "orig" with a direct child "Merge" containing "merged". >> >> [ I also had to expose "VIEW.head = S.head" in Irmin: >> https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 >> and I modified your code slightly to make "parents" optional and to be >> a Commit.t, but that shouldn't make any difference I think. ] >> >>> I'll see if I can add your `make_head` function. >>> >>> Thomas >>> >>>> >>>>>> Currently, I merge to create a new commit, test it, and then do a >>>>>> fast-forward to update the branch to include the merge if the test >>>>>> passes. But if I can use custom merge code, then it would be OK to >>>>>> merge directly to the branch when my merge code returns, since it will >>>>>> already have had a chance to test it. >>>>> >>>>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >>>> >>>> Thanks! [ As noted elsewhere, it would be useful to distinguish the >>>> case where it's already up-to-date (success; no futher action needed) >>>> from the case where it's not an ancestor (failure; retry merge with >>>> new head). ] >>>> >>>>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>>>> >>>>> Best, >>>>> Thomas -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 09 17:48:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 17:48: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 1YgGYc-0006wM-PQ; Thu, 09 Apr 2015 17:48:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgGYa-0006wB-UL for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 17:48:01 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id 73/EA-04861-F4BB6255; Thu, 09 Apr 2015 17:47:59 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1428601678!15079241!1 X-Originating-IP: [209.85.217.170] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5172 invoked from network); 9 Apr 2015 17:47:59 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 17:47:59 -0000 Received: by lbcga7 with SMTP id ga7so47285349lbc.1 for ; Thu, 09 Apr 2015 10:47:58 -0700 (PDT) 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=5uuGP8RSPlt2wWS6Gyt5hPjxHX4ZHZWfnGd8fgODGHA=; b=uYfZNGRDj4yvtZHZL8epWeShIPf8l9zL9txbqVC0wDpdzS+UtfUqwFRPuaqZRJAF+L F0w5CCruYJx2POGB1mDde4GG3E9I9dPsknISTzVyOzEuo1kkYW7dmnzWKo+/l53Hgggg BHXCZbTc9v3B2NkzUeIFcCO0h9NKiPfe3KaHQwUQV+T0bZLu8u6rBvQN17zJmlBqWFq/ Boco8i0AJB7pAnsJRrzyTMAqyXJOmAIsei/1OtinfCy9BTUy60lFKHdEp9yWIgHDZggy 2W2d+O+ECSuJi7SdlCI6cuU+XXQ3LTKxIdCW6twz2IUyXVNyG0y3ETJjAW9+xlUQpt3C L21A== MIME-Version: 1.0 X-Received: by 10.152.44.161 with SMTP id f1mr5420793lam.26.1428601678167; Thu, 09 Apr 2015 10:47:58 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Thu, 9 Apr 2015 10:47:58 -0700 (PDT) In-Reply-To: <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> Date: Thu, 9 Apr 2015 18:47:58 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 April 2015 at 18:22, Thomas Gazagnaire wrote: >>>> BC.make_head : >>>> Irmin.config -> ('a -> Irmin.task) -> parents:head list -> >>>> msg:'a -> View.t -> ('a -> t) Lwt.t > > > Do you really need a View.t here? How do you build that value? Do you first take a view from somewhere and then tweak it to get the value you want for the merge? Or you just run a sequence of updates? There are two cases. If the branch already contains a commit: 1. I use View.of_path to get the view. 2. I use BC.of_head to make a temporary branch. 3. I commit to the temporary branch with View.update_path. 4. After testing the commit, I use BC.compare_and_set_head to commit to the main branch. If the branch is empty: 1. I use View.empty to get the view. 2. I commit directly to the master branch with View.update_path (no testing is possible in this case). This works - it would just be a bit neater if there was a uniform way to make a commit from a view. > I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: > 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; > 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. > 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. > > I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? Sounds good to me. Thanks! > Thomas > > >>>> >>>> to implement CueKeeper's API: >>>> >>>> module Commit : sig >>>> type t >>>> val commit : >>>> parents:t list -> >>>> Staging.t -> >>>> msg:string -> >>>> t Lwt.t >>>> >>>> How can I take two commits, generate a view (manually) with the >>>> results of my custom merge, and then add the result as a new commit >>>> with both of the original parents? >>> >>> Something like: >>> >>> let commit ~parents staging ~msg = >>> match staging.Staging.commit with >>> | None -> assert false >>> | Some t -> >>> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> >>> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; >>> V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> >>> {t with c_store = tmp_branch} >> >> It doesn't seem to work. I tested with this code (on my "test_merging" branch): >> >> https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d >> >> Git.Commit.checkout base >>= fun stage -> >> Git.Staging.update stage ["foo"] "a" >>= fun () -> >> Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> >> Git.Staging.update stage ["foo"] "b" >>= fun () -> >> Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> >> Git.Staging.update stage ["foo"] "merged" >>= fun () -> >> Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> >> Git.Branch.fast_forward_to master result >>= function >> >> For testing, it uses the Git backend with the directory "test_db". >> Looking at the result with gitk, I have an initial commit containing >> "orig" with a direct child "Merge" containing "merged". >> >> [ I also had to expose "VIEW.head = S.head" in Irmin: >> https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 >> and I modified your code slightly to make "parents" optional and to be >> a Commit.t, but that shouldn't make any difference I think. ] >> >>> I'll see if I can add your `make_head` function. >>> >>> Thomas >>> >>>> >>>>>> Currently, I merge to create a new commit, test it, and then do a >>>>>> fast-forward to update the branch to include the merge if the test >>>>>> passes. But if I can use custom merge code, then it would be OK to >>>>>> merge directly to the branch when my merge code returns, since it will >>>>>> already have had a chance to test it. >>>>> >>>>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >>>> >>>> Thanks! [ As noted elsewhere, it would be useful to distinguish the >>>> case where it's already up-to-date (success; no futher action needed) >>>> from the case where it's not an ancestor (failure; retry merge with >>>> new head). ] >>>> >>>>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>>>> >>>>> Best, >>>>> Thomas -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 09 18:18:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 18:18: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 1YgH2H-0002as-C8; Thu, 09 Apr 2015 18:18:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgH2F-0002an-IQ for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 18:18:39 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id CA/7E-13722-E72C6255; Thu, 09 Apr 2015 18:18:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1428603514!16789970!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32225 invoked from network); 9 Apr 2015 18:18:35 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 18:18:35 -0000 Received: by wiax7 with SMTP id x7so314218wia.0 for ; Thu, 09 Apr 2015 11:18:34 -0700 (PDT) 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=Umn9KKGA4xIWVTsOX1LXFiF8xoTQZicbL6Tk9470bPs=; b=lKGVyLdp9p33Jw/A0OdAQ4aAWfNMIDbfd2k6eBKZ3Asmz2ZI2CZwiT+Jl4e9KTVsUK k2jdgRAQTB6SbVDz4Q84zMrNg2pzvJd2/A74ZcQPD8QMWgs6vEHSVOg40QhePy1126Cc 2Flr6iwbKE4qAx4ZhtnLLFXyGI9kFm3eo1w2ed4MbOhEsi2JrbFKVZO5nbpXBk2vUXvu jgtu8sxwjC+AMqAPriTu79uv8lNcYcvUxPjSMk27BH+ryOXpe+0Q5CjK2EBASk0lL9iI BuCbG8C6mOfM4shdBUaACuGzKy0XgA1sj3d15Prycmlw3ajz8o9LouZUL6qBQ/CZGdka sZIw== X-Received: by 10.180.76.137 with SMTP id k9mr3901869wiw.4.1428603514656; Thu, 09 Apr 2015 11:18:34 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id ax10sm21150528wjc.26.2015.04.09.11.18.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 11:18:33 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 9 Apr 2015 20:18:31 +0200 Message-Id: References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 > There are two cases. If the branch already contains a commit: > 1. I use View.of_path to get the view. > 2. I use BC.of_head to make a temporary branch. > 3. I commit to the temporary branch with View.update_path. > 4. After testing the commit, I use BC.compare_and_set_head to commit > to the main branch. > > If the branch is empty: > 1. I use View.empty to get the view. > 2. I commit directly to the master branch with View.update_path (no > testing is possible in this case). > > This works - it would just be a bit neater if there was a uniform way > to make a commit from a view. Agreed. I have a ticket open to be able to start an empty store with a named branch. I should fix it and that should help. > >> I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: >> 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; >> 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. >> 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. >> >> I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? > > Sounds good to me. Thanks! I've done that in https://github.com/mirage/irmin/pull/188 Thomas > >> Thomas >> >> >>>>> >>>>> to implement CueKeeper's API: >>>>> >>>>> module Commit : sig >>>>> type t >>>>> val commit : >>>>> parents:t list -> >>>>> Staging.t -> >>>>> msg:string -> >>>>> t Lwt.t >>>>> >>>>> How can I take two commits, generate a view (manually) with the >>>>> results of my custom merge, and then add the result as a new commit >>>>> with both of the original parents? >>>> >>>> Something like: >>>> >>>> let commit ~parents staging ~msg = >>>> match staging.Staging.commit with >>>> | None -> assert false >>>> | Some t -> >>>> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> >>>> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; >>>> V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> >>>> {t with c_store = tmp_branch} >>> >>> It doesn't seem to work. I tested with this code (on my "test_merging" branch): >>> >>> https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d >>> >>> Git.Commit.checkout base >>= fun stage -> >>> Git.Staging.update stage ["foo"] "a" >>= fun () -> >>> Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> >>> Git.Staging.update stage ["foo"] "b" >>= fun () -> >>> Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> >>> Git.Staging.update stage ["foo"] "merged" >>= fun () -> >>> Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> >>> Git.Branch.fast_forward_to master result >>= function >>> >>> For testing, it uses the Git backend with the directory "test_db". >>> Looking at the result with gitk, I have an initial commit containing >>> "orig" with a direct child "Merge" containing "merged". >>> >>> [ I also had to expose "VIEW.head = S.head" in Irmin: >>> https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 >>> and I modified your code slightly to make "parents" optional and to be >>> a Commit.t, but that shouldn't make any difference I think. ] >>> >>>> I'll see if I can add your `make_head` function. >>>> >>>> Thomas >>>> >>>>> >>>>>>> Currently, I merge to create a new commit, test it, and then do a >>>>>>> fast-forward to update the branch to include the merge if the test >>>>>>> passes. But if I can use custom merge code, then it would be OK to >>>>>>> merge directly to the branch when my merge code returns, since it will >>>>>>> already have had a chance to test it. >>>>>> >>>>>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >>>>> >>>>> Thanks! [ As noted elsewhere, it would be useful to distinguish the >>>>> case where it's already up-to-date (success; no futher action needed) >>>>> from the case where it's not an ancestor (failure; retry merge with >>>>> new head). ] >>>>> >>>>>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>>>>> >>>>>> Best, >>>>>> Thomas > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > 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 Thu Apr 09 18:18:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 18:18: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 1YgH2H-0002as-C8; Thu, 09 Apr 2015 18:18:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgH2F-0002an-IQ for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 18:18:39 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id CA/7E-13722-E72C6255; Thu, 09 Apr 2015 18:18:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1428603514!16789970!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32225 invoked from network); 9 Apr 2015 18:18:35 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 18:18:35 -0000 Received: by wiax7 with SMTP id x7so314218wia.0 for ; Thu, 09 Apr 2015 11:18:34 -0700 (PDT) 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=Umn9KKGA4xIWVTsOX1LXFiF8xoTQZicbL6Tk9470bPs=; b=lKGVyLdp9p33Jw/A0OdAQ4aAWfNMIDbfd2k6eBKZ3Asmz2ZI2CZwiT+Jl4e9KTVsUK k2jdgRAQTB6SbVDz4Q84zMrNg2pzvJd2/A74ZcQPD8QMWgs6vEHSVOg40QhePy1126Cc 2Flr6iwbKE4qAx4ZhtnLLFXyGI9kFm3eo1w2ed4MbOhEsi2JrbFKVZO5nbpXBk2vUXvu jgtu8sxwjC+AMqAPriTu79uv8lNcYcvUxPjSMk27BH+ryOXpe+0Q5CjK2EBASk0lL9iI BuCbG8C6mOfM4shdBUaACuGzKy0XgA1sj3d15Prycmlw3ajz8o9LouZUL6qBQ/CZGdka sZIw== X-Received: by 10.180.76.137 with SMTP id k9mr3901869wiw.4.1428603514656; Thu, 09 Apr 2015 11:18:34 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id ax10sm21150528wjc.26.2015.04.09.11.18.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 11:18:33 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 9 Apr 2015 20:18:31 +0200 Message-Id: References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 > There are two cases. If the branch already contains a commit: > 1. I use View.of_path to get the view. > 2. I use BC.of_head to make a temporary branch. > 3. I commit to the temporary branch with View.update_path. > 4. After testing the commit, I use BC.compare_and_set_head to commit > to the main branch. > > If the branch is empty: > 1. I use View.empty to get the view. > 2. I commit directly to the master branch with View.update_path (no > testing is possible in this case). > > This works - it would just be a bit neater if there was a uniform way > to make a commit from a view. Agreed. I have a ticket open to be able to start an empty store with a named branch. I should fix it and that should help. > >> I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: >> 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; >> 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. >> 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. >> >> I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? > > Sounds good to me. Thanks! I've done that in https://github.com/mirage/irmin/pull/188 Thomas > >> Thomas >> >> >>>>> >>>>> to implement CueKeeper's API: >>>>> >>>>> module Commit : sig >>>>> type t >>>>> val commit : >>>>> parents:t list -> >>>>> Staging.t -> >>>>> msg:string -> >>>>> t Lwt.t >>>>> >>>>> How can I take two commits, generate a view (manually) with the >>>>> results of my custom merge, and then add the result as a new commit >>>>> with both of the original parents? >>>> >>>> Something like: >>>> >>>> let commit ~parents staging ~msg = >>>> match staging.Staging.commit with >>>> | None -> assert false >>>> | Some t -> >>>> I.of_head t.c_repo.config t.c_repo.task_maker (id t) >>= fun tmp_branch -> >>>> (* THE ONLY CHANGE *) V.set_parents Staging.view parents; >>>> V.update_path (tmp_branch msg) I.Key.empty staging.Staging.view >|= fun () -> >>>> {t with c_store = tmp_branch} >>> >>> It doesn't seem to work. I tested with this code (on my "test_merging" branch): >>> >>> https://github.com/talex5/cuekeeper/commit/4da442f91422bd6b8654922ca6955cf78cd9d83d >>> >>> Git.Commit.checkout base >>= fun stage -> >>> Git.Staging.update stage ["foo"] "a" >>= fun () -> >>> Git.Commit.commit ~parents:[base] ~msg:"A" stage >>= fun a -> >>> Git.Staging.update stage ["foo"] "b" >>= fun () -> >>> Git.Commit.commit ~parents:[base] ~msg:"B" stage >>= fun b -> >>> Git.Staging.update stage ["foo"] "merged" >>= fun () -> >>> Git.Commit.commit ~parents:[a; b] ~msg:"Merge" stage >>= fun result -> >>> Git.Branch.fast_forward_to master result >>= function >>> >>> For testing, it uses the Git backend with the directory "test_db". >>> Looking at the result with gitk, I have an initial commit containing >>> "orig" with a direct child "Merge" containing "merged". >>> >>> [ I also had to expose "VIEW.head = S.head" in Irmin: >>> https://github.com/talex5/irmin/commit/d77f81c0786860a58a8a596bca8426d1e1f98661 >>> and I modified your code slightly to make "parents" optional and to be >>> a Commit.t, but that shouldn't make any difference I think. ] >>> >>>> I'll see if I can add your `make_head` function. >>>> >>>> Thomas >>>> >>>>> >>>>>>> Currently, I merge to create a new commit, test it, and then do a >>>>>>> fast-forward to update the branch to include the merge if the test >>>>>>> passes. But if I can use custom merge code, then it would be OK to >>>>>>> merge directly to the branch when my merge code returns, since it will >>>>>>> already have had a chance to test it. >>>>>> >>>>>> In the PR, I've also added `Irmin.fast_forward_head` (maybe it should be `fast_forward_to_head`?) to to that. It returns "false" (and does nothing) it the new head is not strictly in the future of the current head. >>>>> >>>>> Thanks! [ As noted elsewhere, it would be useful to distinguish the >>>>> case where it's already up-to-date (success; no futher action needed) >>>>> from the case where it's not an ancestor (failure; retry merge with >>>>> new head). ] >>>>> >>>>>> Let me know if you need something else (I'm still working on the right way to fix the watch API). >>>>>> >>>>>> Best, >>>>>> Thomas > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > 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 Thu Apr 09 18:30:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 18:30: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 1YgHDT-00048Q-1a; Thu, 09 Apr 2015 18:30:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgHDS-00047C-0E for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 18:30:14 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 6A/FD-23827-535C6255; Thu, 09 Apr 2015 18:30:13 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1428604212!16771530!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3763 invoked from network); 9 Apr 2015 18:30:12 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 18:30:12 -0000 Received: by wgsk9 with SMTP id k9so106569314wgs.3 for ; Thu, 09 Apr 2015 11:30:12 -0700 (PDT) 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=wBsS3p1D8kK8HCk9Xa0tryn89sDWdAGEDSnI7k5RAh8=; b=lNiIKFVW5vntpaulJaCt8Uh5vVUna4P9G3DxcJHbryzdkqeY/3G8dgyJXBtp7HTdmr As5Q8mb5aSdL89gnoGVyjYm+QdRnDyUYWZqDVCk8/p5fwONeYubMlQnCkMGvCkbr6C7r tOsy+190qrUuhzcgcdtVAMSWRaM09giiZSU2f+TtqeGU+xMUmGCQ6LDRi4P/0TJK05CU y8PcxcW9umvq6I3iWiyEkInrdLKbs0NXrRq8S9fOjsYTIgQ7BHwszpBOHtnVkIiLZCNm 017+rbf6m0oc44bIBhs6BlpjGEVMdlj7mXPltbmzOwRgmTAFCDm/x3+mAV9Nk04vD70O XL/w== X-Received: by 10.194.77.44 with SMTP id p12mr40557209wjw.1.1428604212424; Thu, 09 Apr 2015 11:30:12 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id cf12sm21197394wjb.10.2015.04.09.11.30.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 11:30:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: <5526B66C.2000601@somerandomidiot.com> Date: Thu, 9 Apr 2015 20:30:10 +0200 Message-Id: References: <5526B66C.2000601@somerandomidiot.com> To: Mindy X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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 that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. > > Thanks for your consideration and support. :) That's awesome! I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? If yes, a good way to stress test the system is to (1) generate a big history of stuff and (2) use git reset --hard to revert to arbitrary points in the past (which are supposed to be consistent) and check that nothing breaks badly (this is a good test for intermediate caches for instances). In a distributed settings, if you keep track of the state of multiple unikernels, you can try to verify that global invariants (involving multiple unikernels) still hold. Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) 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 Apr 09 18:30:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 18:30: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 1YgHDT-00048Q-1a; Thu, 09 Apr 2015 18:30:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgHDS-00047C-0E for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 18:30:14 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 6A/FD-23827-535C6255; Thu, 09 Apr 2015 18:30:13 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1428604212!16771530!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3763 invoked from network); 9 Apr 2015 18:30:12 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 18:30:12 -0000 Received: by wgsk9 with SMTP id k9so106569314wgs.3 for ; Thu, 09 Apr 2015 11:30:12 -0700 (PDT) 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=wBsS3p1D8kK8HCk9Xa0tryn89sDWdAGEDSnI7k5RAh8=; b=lNiIKFVW5vntpaulJaCt8Uh5vVUna4P9G3DxcJHbryzdkqeY/3G8dgyJXBtp7HTdmr As5Q8mb5aSdL89gnoGVyjYm+QdRnDyUYWZqDVCk8/p5fwONeYubMlQnCkMGvCkbr6C7r tOsy+190qrUuhzcgcdtVAMSWRaM09giiZSU2f+TtqeGU+xMUmGCQ6LDRi4P/0TJK05CU y8PcxcW9umvq6I3iWiyEkInrdLKbs0NXrRq8S9fOjsYTIgQ7BHwszpBOHtnVkIiLZCNm 017+rbf6m0oc44bIBhs6BlpjGEVMdlj7mXPltbmzOwRgmTAFCDm/x3+mAV9Nk04vD70O XL/w== X-Received: by 10.194.77.44 with SMTP id p12mr40557209wjw.1.1428604212424; Thu, 09 Apr 2015 11:30:12 -0700 (PDT) Received: from [192.168.1.44] (car06-8-83-155-104-81.fbx.proxad.net. [83.155.104.81]) by mx.google.com with ESMTPSA id cf12sm21197394wjb.10.2015.04.09.11.30.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 11:30:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: <5526B66C.2000601@somerandomidiot.com> Date: Thu, 9 Apr 2015 20:30:10 +0200 Message-Id: References: <5526B66C.2000601@somerandomidiot.com> To: Mindy X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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 that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. > > Thanks for your consideration and support. :) That's awesome! I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? If yes, a good way to stress test the system is to (1) generate a big history of stuff and (2) use git reset --hard to revert to arbitrary points in the past (which are supposed to be consistent) and check that nothing breaks badly (this is a good test for intermediate caches for instances). In a distributed settings, if you keep track of the state of multiple unikernels, you can try to verify that global invariants (involving multiple unikernels) still hold. Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) 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 Apr 09 20:19:06 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 20:19:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgIuj-0001l2-KN; Thu, 09 Apr 2015 20:19:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgIuh-0001kx-LR for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 20:18:59 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 7F/62-09809-2BED6255; Thu, 09 Apr 2015 20:18:58 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1428610737!10707096!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17507 invoked from network); 9 Apr 2015 20:18:58 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 20:18:58 -0000 Received: by lbcga7 with SMTP id ga7so50241164lbc.1 for ; Thu, 09 Apr 2015 13:18:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-disposition:user-agent; bh=2wypmlZT5L+iD37S3OfmSe45NW20cyso5Nhryzw/idc=; b=NNRgw2xuYPtpS2vdhgTgpW2vf7wqoP8k/4BsoSQkSkN+ryn6eAwbL5z6n/acZqHP6D RYhHotSyiRdzxeaWUgn6V78RYJCNEmmGwN9fwzJka7UHm1EaY/POgNbw7JgfMwCzx17c NwnIchwgmY4+yqUYyiz/uxy0WjzoeZS8wCHpNS7cx6zS9k5laT0X3Mco9kNsuaK9b5TF oTb4f4K51KhziqiQTKuvDzwbP1KWW8kWNs5hKgVDADXJgQ/FszFsKBb09PVsjwM6MoXJ Ll7bHGyL8EVrjMHrQl+P8fxbrG/KS9SQqXrxsbMq8YoBliYUWg4UgUz8M8cqfyPlqAoF kj8A== X-Gm-Message-State: ALoCoQnXWiV6vR/+/GjSAGlSnaUfOWxHSqT/GUms6Ibl4vy2/yO+A/upblkZ06gaf+1ETO16m4d5 X-Received: by 10.112.185.101 with SMTP id fb5mr30200924lbc.12.1428610737316; Thu, 09 Apr 2015 13:18:57 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id dw11sm3441490lbd.38.2015.04.09.13.18.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 13:18:56 -0700 (PDT) Date: Thu, 9 Apr 2015 22:18:53 +0200 From: Magnus Therning To: mirageos-devel Message-ID: <20150409201853.GA11002@tatooine> MIME-Version: 1.0 User-Agent: Mutt/1.5.23 (2014-03-12) Subject: [MirageOS-devel] More troubles with tcp on ARM 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="===============1436299470964633742==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1436299470964633742== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable My attempts to get tcp working in a VM on ARM continue. Now I've dropped cohttp and moved down to straight tcp/udp instead. The following is the code of a simple server: ~~~ open V1_LWT open Lwt open Printf module Main (C:CONSOLE) (S:STACKV4) =3D struct module T =3D S.TCPV4 let rec tcp_echo console flow =3D T.read flow >>=3D function | `Eof -> T.close flow | `Error _ -> T.close flow | `Ok b -> C.log_s console (sprintf " %d - %s" (Cstruct.len b) = (Cstruct.to_string b)) >>=3D fun () -> T.write flow b >>=3D function | `Eof -> T.close flow | `Error _ -> T.close flow | `Ok () -> tcp_echo console flow let start console stack =3D S.listen_udpv4 stack 18081 ( fun ~src ~dst ~src_port b -> C.log_s console (sprintf "udp: %s:%d" (Ipaddr.V4.to_string = src) src_port) >>=3D fun () -> C.log_s console (sprintf " udp: %d - %s" (C= struct.len b) (Cstruct.to_string b)) ); S.listen_tcpv4 stack 18080 ( fun flow -> let dst, dst_port =3D T.get_dest flow in C.log_s console (sprintf "tcp: %s:%d" (Ipaddr.V4.to_string = dst) dst_port) >>=3D fun () -> tcp_echo console flow ); S.listen stack end ~~~ It works fine in Unix mode, both on x86 and on my cubietruck board. When built in Xen mode though it doesn't work as well. When run in Unix mode I see the expected behaviour: shell my server console ----- ----------------- % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 udp: 6 - hello % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 hello 6 - hello % echo foobar | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 foobar 6 - foobar When running the server in a VM on ARM I see the same behaviour for UDP, but for TCP it changes. shell my server console ----- ----------------- % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 udp: 6 - hello % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 6 - 6 - Yupp, the string is printed twice, it has a length, but it's missing actual data! Any pointers as to where to start looking would be much appreciated, as well as confirmation that this really is an issue and not just a user error ;) /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus For a successful technology, reality must take precedence over public relations, for nature cannot be fooled. -- R.P. Feynman --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUm3qcACgkQiMWTaatN+6RY6ACfW+Xndirt+IFsP0IeXM0WLsgs UhwAoKUw7AUrMrOm4CdXsqaNiRxVNxXi =R22v -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- --===============1436299470964633742== 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 --===============1436299470964633742==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 09 20:19:06 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 20:19:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgIuj-0001l2-KN; Thu, 09 Apr 2015 20:19:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgIuh-0001kx-LR for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 20:18:59 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 7F/62-09809-2BED6255; Thu, 09 Apr 2015 20:18:58 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1428610737!10707096!1 X-Originating-IP: [209.85.217.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17507 invoked from network); 9 Apr 2015 20:18:58 -0000 Received: from mail-lb0-f172.google.com (HELO mail-lb0-f172.google.com) (209.85.217.172) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Apr 2015 20:18:58 -0000 Received: by lbcga7 with SMTP id ga7so50241164lbc.1 for ; Thu, 09 Apr 2015 13:18:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-disposition:user-agent; bh=2wypmlZT5L+iD37S3OfmSe45NW20cyso5Nhryzw/idc=; b=NNRgw2xuYPtpS2vdhgTgpW2vf7wqoP8k/4BsoSQkSkN+ryn6eAwbL5z6n/acZqHP6D RYhHotSyiRdzxeaWUgn6V78RYJCNEmmGwN9fwzJka7UHm1EaY/POgNbw7JgfMwCzx17c NwnIchwgmY4+yqUYyiz/uxy0WjzoeZS8wCHpNS7cx6zS9k5laT0X3Mco9kNsuaK9b5TF oTb4f4K51KhziqiQTKuvDzwbP1KWW8kWNs5hKgVDADXJgQ/FszFsKBb09PVsjwM6MoXJ Ll7bHGyL8EVrjMHrQl+P8fxbrG/KS9SQqXrxsbMq8YoBliYUWg4UgUz8M8cqfyPlqAoF kj8A== X-Gm-Message-State: ALoCoQnXWiV6vR/+/GjSAGlSnaUfOWxHSqT/GUms6Ibl4vy2/yO+A/upblkZ06gaf+1ETO16m4d5 X-Received: by 10.112.185.101 with SMTP id fb5mr30200924lbc.12.1428610737316; Thu, 09 Apr 2015 13:18:57 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id dw11sm3441490lbd.38.2015.04.09.13.18.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 13:18:56 -0700 (PDT) Date: Thu, 9 Apr 2015 22:18:53 +0200 From: Magnus Therning To: mirageos-devel Message-ID: <20150409201853.GA11002@tatooine> MIME-Version: 1.0 User-Agent: Mutt/1.5.23 (2014-03-12) Subject: [MirageOS-devel] More troubles with tcp on ARM 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="===============1436299470964633742==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1436299470964633742== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable My attempts to get tcp working in a VM on ARM continue. Now I've dropped cohttp and moved down to straight tcp/udp instead. The following is the code of a simple server: ~~~ open V1_LWT open Lwt open Printf module Main (C:CONSOLE) (S:STACKV4) =3D struct module T =3D S.TCPV4 let rec tcp_echo console flow =3D T.read flow >>=3D function | `Eof -> T.close flow | `Error _ -> T.close flow | `Ok b -> C.log_s console (sprintf " %d - %s" (Cstruct.len b) = (Cstruct.to_string b)) >>=3D fun () -> T.write flow b >>=3D function | `Eof -> T.close flow | `Error _ -> T.close flow | `Ok () -> tcp_echo console flow let start console stack =3D S.listen_udpv4 stack 18081 ( fun ~src ~dst ~src_port b -> C.log_s console (sprintf "udp: %s:%d" (Ipaddr.V4.to_string = src) src_port) >>=3D fun () -> C.log_s console (sprintf " udp: %d - %s" (C= struct.len b) (Cstruct.to_string b)) ); S.listen_tcpv4 stack 18080 ( fun flow -> let dst, dst_port =3D T.get_dest flow in C.log_s console (sprintf "tcp: %s:%d" (Ipaddr.V4.to_string = dst) dst_port) >>=3D fun () -> tcp_echo console flow ); S.listen stack end ~~~ It works fine in Unix mode, both on x86 and on my cubietruck board. When built in Xen mode though it doesn't work as well. When run in Unix mode I see the expected behaviour: shell my server console ----- ----------------- % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 udp: 6 - hello % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 hello 6 - hello % echo foobar | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 foobar 6 - foobar When running the server in a VM on ARM I see the same behaviour for UDP, but for TCP it changes. shell my server console ----- ----------------- % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 udp: 6 - hello % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 6 - 6 - Yupp, the string is printed twice, it has a length, but it's missing actual data! Any pointers as to where to start looking would be much appreciated, as well as confirmation that this really is an issue and not just a user error ;) /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus For a successful technology, reality must take precedence over public relations, for nature cannot be fooled. -- R.P. Feynman --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUm3qcACgkQiMWTaatN+6RY6ACfW+Xndirt+IFsP0IeXM0WLsgs UhwAoKUw7AUrMrOm4CdXsqaNiRxVNxXi =R22v -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- --===============1436299470964633742== 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 --===============1436299470964633742==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 09 21:19:00 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 21:19: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 1YgJqd-0000hp-Pg; Thu, 09 Apr 2015 21:18:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgJqc-0000hk-Nz for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 21:18:50 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id DD/B7-13722-ABCE6255; Thu, 09 Apr 2015 21:18:50 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1428614329!16794770!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11749 invoked from network); 9 Apr 2015 21:18:49 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 21:18:49 -0000 Received: from [192.168.0.6] (cpc16-cmbg15-2-0-cust21.5-4.cable.virginm.net [86.5.162.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (not verified)) by mail.mehnert.org (Postfix) with ESMTPS id 4F55A1C95 for ; Thu, 9 Apr 2015 23:18:48 +0200 (CEST) Message-ID: <5526EC9D.2040402@mehnert.org> Date: Thu, 09 Apr 2015 22:18:21 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: mirageos-devel OpenPGP: id=DF7C28EE Subject: [MirageOS-devel] podcast about TLS & MirageOS 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 hey, I recorded with two friends of mine a podcast on TLS; how to develop security protocols which are readable, fast, robust; and also MirageOS. It is in German and roughly 2 hours; I'm happy for feedback and any questions http://monoxyd.de/20150408-ohm-008-ohne-heftige-mangel cheers, hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVJuydAAoJELyJZYjffCjutpMP/3gXwtCYAVj4l3ecV5eNPgII fqcyzCR7Fnvi9zpuZ4pwaK8C1H7ujs7+nKizTB6W2dtwRrRF4cxIv7kqd+mJcY1B Zs9NmGKhcQH7XMgf3qZiS4qyW298mjKVPZoOGBNeoQVRWcUJUwQQsw9ITURhR/OU AMOrSvMqESPM3CnGFMtQbcp91ZJaGUVZCox2dTiX4Orl+aQu27IbWAvrjBZ7c30V gLnkInwxt64+X7K/xVBJEOLJiCleosnJjCud3xAWQOVQuRlDOL8TNOFlaa8YmDWs l5UjuM07jlczVb3p3if931yNvQ2PHpeZFHC/3NIMePw1jzro4vVcvByWv/PNtRfZ ZHT+HyXx9SvWp/tZB2J21rDULkbBxdC55NUWSnv83IWfJTt3hWUel6Yw8lIwn9tq 5yEf/GSKN7IQryD6Is1OpaYLWAaHmWaoKXsHk+YRPrsSdKP8D/6XY5ZLuvx55Z4R HPWQ7HPqou0Cr92bCzvQ/gMuE8KUuWodfRXlHwGMyyxwKQWdE8KGnYWP1BGMHXhT mw8A6EKVzky0n+nB1HqGyNZRYi/kC6wQNKy3mGWTl1WN2tb7MkgUdaC7p8XjsAn+ t+Uh4jdiDbs7mLTvNzMXUecWaamohs95T5yIDHejR/Z0QKsHmYREtdUh2zZH0Fti rXza4zg9h00uNS+9+nZy =glNZ -----END PGP SIGNATURE----- _______________________________________________ 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 Apr 09 21:19:00 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 21:19: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 1YgJqd-0000hp-Pg; Thu, 09 Apr 2015 21:18:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgJqc-0000hk-Nz for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 21:18:50 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id DD/B7-13722-ABCE6255; Thu, 09 Apr 2015 21:18:50 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1428614329!16794770!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11749 invoked from network); 9 Apr 2015 21:18:49 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 21:18:49 -0000 Received: from [192.168.0.6] (cpc16-cmbg15-2-0-cust21.5-4.cable.virginm.net [86.5.162.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (not verified)) by mail.mehnert.org (Postfix) with ESMTPS id 4F55A1C95 for ; Thu, 9 Apr 2015 23:18:48 +0200 (CEST) Message-ID: <5526EC9D.2040402@mehnert.org> Date: Thu, 09 Apr 2015 22:18:21 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: mirageos-devel OpenPGP: id=DF7C28EE Subject: [MirageOS-devel] podcast about TLS & MirageOS 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 hey, I recorded with two friends of mine a podcast on TLS; how to develop security protocols which are readable, fast, robust; and also MirageOS. It is in German and roughly 2 hours; I'm happy for feedback and any questions http://monoxyd.de/20150408-ohm-008-ohne-heftige-mangel cheers, hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVJuydAAoJELyJZYjffCjutpMP/3gXwtCYAVj4l3ecV5eNPgII fqcyzCR7Fnvi9zpuZ4pwaK8C1H7ujs7+nKizTB6W2dtwRrRF4cxIv7kqd+mJcY1B Zs9NmGKhcQH7XMgf3qZiS4qyW298mjKVPZoOGBNeoQVRWcUJUwQQsw9ITURhR/OU AMOrSvMqESPM3CnGFMtQbcp91ZJaGUVZCox2dTiX4Orl+aQu27IbWAvrjBZ7c30V gLnkInwxt64+X7K/xVBJEOLJiCleosnJjCud3xAWQOVQuRlDOL8TNOFlaa8YmDWs l5UjuM07jlczVb3p3if931yNvQ2PHpeZFHC/3NIMePw1jzro4vVcvByWv/PNtRfZ ZHT+HyXx9SvWp/tZB2J21rDULkbBxdC55NUWSnv83IWfJTt3hWUel6Yw8lIwn9tq 5yEf/GSKN7IQryD6Is1OpaYLWAaHmWaoKXsHk+YRPrsSdKP8D/6XY5ZLuvx55Z4R HPWQ7HPqou0Cr92bCzvQ/gMuE8KUuWodfRXlHwGMyyxwKQWdE8KGnYWP1BGMHXhT mw8A6EKVzky0n+nB1HqGyNZRYi/kC6wQNKy3mGWTl1WN2tb7MkgUdaC7p8XjsAn+ t+Uh4jdiDbs7mLTvNzMXUecWaamohs95T5yIDHejR/Z0QKsHmYREtdUh2zZH0Fti rXza4zg9h00uNS+9+nZy =glNZ -----END PGP SIGNATURE----- _______________________________________________ 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 Apr 09 21:40:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 21:40: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 1YgKBX-0003Mm-BL; Thu, 09 Apr 2015 21:40:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgKBW-0003Ky-IK for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 21:40:26 +0000 Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id 8F/CE-24632-9C1F6255; Thu, 09 Apr 2015 21:40:25 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1428615625!15166518!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29903 invoked from network); 9 Apr 2015 21:40:25 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 21:40:25 -0000 Received: from mfilter40-d.gandi.net (mfilter40-d.gandi.net [217.70.178.171]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 1B158FB887; Thu, 9 Apr 2015 23:40:25 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter40-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter40-d.gandi.net (mfilter40-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id y3RGdP6bzlAX; Thu, 9 Apr 2015 23:40:23 +0200 (CEST) X-Originating-IP: 88.96.19.110 Received: from [192.168.1.237] (88-96-19-110.dsl.zen.co.uk [88.96.19.110]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 817ADFB86E; Thu, 9 Apr 2015 23:40:23 +0200 (CEST) Message-ID: <5526F1A8.7040203@somerandomidiot.com> Date: Thu, 09 Apr 2015 22:39:52 +0100 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Thomas Gazagnaire References: <5526B66C.2000601@somerandomidiot.com> In-Reply-To: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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-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 04/09/2015 07:30 PM, Thomas Gazagnaire wrote: >> I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. >> >> Thanks for your consideration and support. :) > That's awesome! > > I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? Yes, it should work this way (once there's more code in place). > If yes, a good way to stress test the system is to (1) generate a big history of stuff and (2) use git reset --hard to revert to arbitrary points in the past (which are supposed to be consistent) and check that nothing breaks badly (this is a good test for intermediate caches for instances). In a distributed settings, if you keep track of the state of multiple unikernels, you can try to verify that global invariants (involving multiple unikernels) still hold. Ah, that's a good suggestion. Thank you! > > Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) I'd been thinking about (or maybe remembered talking about with someone else?) pre-seeding newly booted unikernels with caches reflecting the current state of the local network, which is a less general case of what you propose. -Mindy _______________________________________________ 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 Apr 09 21:40:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 09 Apr 2015 21:40: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 1YgKBX-0003Mm-BL; Thu, 09 Apr 2015 21:40:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgKBW-0003Ky-IK for mirageos-devel@lists.xenproject.org; Thu, 09 Apr 2015 21:40:26 +0000 Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id 8F/CE-24632-9C1F6255; Thu, 09 Apr 2015 21:40:25 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1428615625!15166518!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29903 invoked from network); 9 Apr 2015 21:40:25 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Apr 2015 21:40:25 -0000 Received: from mfilter40-d.gandi.net (mfilter40-d.gandi.net [217.70.178.171]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 1B158FB887; Thu, 9 Apr 2015 23:40:25 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter40-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter40-d.gandi.net (mfilter40-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id y3RGdP6bzlAX; Thu, 9 Apr 2015 23:40:23 +0200 (CEST) X-Originating-IP: 88.96.19.110 Received: from [192.168.1.237] (88-96-19-110.dsl.zen.co.uk [88.96.19.110]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 817ADFB86E; Thu, 9 Apr 2015 23:40:23 +0200 (CEST) Message-ID: <5526F1A8.7040203@somerandomidiot.com> Date: Thu, 09 Apr 2015 22:39:52 +0100 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Thomas Gazagnaire References: <5526B66C.2000601@somerandomidiot.com> In-Reply-To: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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-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 04/09/2015 07:30 PM, Thomas Gazagnaire wrote: >> I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. >> >> Thanks for your consideration and support. :) > That's awesome! > > I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? Yes, it should work this way (once there's more code in place). > If yes, a good way to stress test the system is to (1) generate a big history of stuff and (2) use git reset --hard to revert to arbitrary points in the past (which are supposed to be consistent) and check that nothing breaks badly (this is a good test for intermediate caches for instances). In a distributed settings, if you keep track of the state of multiple unikernels, you can try to verify that global invariants (involving multiple unikernels) still hold. Ah, that's a good suggestion. Thank you! > > Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) I'd been thinking about (or maybe remembered talking about with someone else?) pre-seeding newly booted unikernels with caches reflecting the current state of the local network, which is a less general case of what you propose. -Mindy _______________________________________________ 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 Apr 10 04:29:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 04:29: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 1YgQZc-0002ps-EC; Fri, 10 Apr 2015 04:29:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgQZa-0002pl-3T for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 04:29:42 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id B5/62-12069-5B157255; Fri, 10 Apr 2015 04:29:41 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1428640180!15207082!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8447 invoked from network); 10 Apr 2015 04:29:40 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2015 04:29:40 -0000 Received: by layy10 with SMTP id y10so4962924lay.0 for ; Thu, 09 Apr 2015 21:29:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=uOKskOG/Q2Cn3dHFDbxGJo9RzqDKiHEXtH34o+Wckvw=; b=Qx81XmI2pT7aJXPB8A+3NpTdCAUaO0px65uJmTrgbH2AkSYmB6sMygNHK56QsKAG2i ITzSb1nb1KJNH6OqxBzcxtgxSAGyqknrDVL+YwkZWlMkQO74XvGOyxYXFmmh17h/FgSZ R16J9n6KXNooSLUYk3bTVV3hE0DgJS018RlCYmrkxGV5AVD18C/Q5kWJpTDUc6lth9+o v25RfevAsSHNr/odf4cfs33zD/Ms7Ir+sggMZ++rwlvrxNuoX75gz1JIi2o5cl6vLUt3 9VIAYaTszPmKu4B+u4I2eBJGFzvUNNp5hM8aDCDIdp0nvOl6s18McJuw1LKwfFd8o5Ch 8KfA== X-Gm-Message-State: ALoCoQknxMV2ix7fGYPMqQytu2G0KG6j2t1mMW6n+BZbns2RQgX8BfwXs/h+kNmx7YVGqah6exCD X-Received: by 10.152.23.99 with SMTP id l3mr7454013laf.61.1428640179552; Thu, 09 Apr 2015 21:29:39 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id bj2sm166318lbc.43.2015.04.09.21.29.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 21:29:38 -0700 (PDT) Date: Fri, 10 Apr 2015 06:29:35 +0200 From: Magnus Therning To: mirageos-devel Message-ID: <20150410042935.GA27321@tatooine> References: <20150409201853.GA11002@tatooine> MIME-Version: 1.0 In-Reply-To: <20150409201853.GA11002@tatooine> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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="===============1354735230147095097==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1354735230147095097== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: [...] >=20 > It works fine in Unix mode, both on x86 and on my cubietruck board. > When built in Xen mode though it doesn't work as well. >=20 > When run in Unix mode I see the expected behaviour: >=20 > shell my server console > ----- ----------------- > % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 > udp: 6 - hello >=20 > % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 > hello 6 - hello >=20 > % echo foobar | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 > foobar 6 - foobar That last line should of course read foobar 7 - foobar That was caused by a copy-paste mistake of mine. > When running the server in a VM on ARM I see the same behaviour for > UDP, but for TCP it changes. >=20 > shell my server console > ----- ----------------- > % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 > udp: 6 - hello >=20 > % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 > 6 - > 6 - And here there are even more copy-paste mistakes. I must have been tired yesterday. Just disregard the `localhost` and `127.0.0.1`, that should of course be the IPs of my cubietruck and my PC, respectively. I did a little bit more testing of this just now, and found something surprising. This is against a VM on ARM: ~~~ % echo thisisalongerstring | ncat -4 192.168.0.33 18080 alongerstring -> tcp: 192.168.0.11:48731 6 -=20 14 - alongerstring ~~~ and ~~~ % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 18080 alongerstringandthisislongerstill -> tcp: 192.168.0.11:48732 6 -=20 34 - alongerstringandthisislongerstill ~~~ and if I send a string that is shorter than 6 characters (I'm guessing including the trailing \r\n), then `ncat` hangs and on the ARM I only see a single line of "length - content": ~~~ tcp: 192.168.0.11:48766 6 - ~~~ I do wonder where those initial 6 characters go... /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus "Sendmail" and "make" are two well known programs that are pretty widely regarded as being debugged into existence. That's why their command languages are so poorly thought out and difficult to learn. It's not just you -- everyone finds them troublesome. -- Peter van der Linden, Expert C Programming, p. 220 --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUnUa8ACgkQiMWTaatN+6RIygCfaTAgMSHGUUJ6D22mDEN8pXad ZygAnRrQEz14/xa2PMfYDelfy/qiEs/7 =/B/y -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- --===============1354735230147095097== 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 --===============1354735230147095097==-- From mirageos-devel-bounces@lists.xenproject.org Fri Apr 10 04:29:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 04:29: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 1YgQZc-0002ps-EC; Fri, 10 Apr 2015 04:29:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgQZa-0002pl-3T for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 04:29:42 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id B5/62-12069-5B157255; Fri, 10 Apr 2015 04:29:41 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1428640180!15207082!1 X-Originating-IP: [209.85.215.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8447 invoked from network); 10 Apr 2015 04:29:40 -0000 Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2015 04:29:40 -0000 Received: by layy10 with SMTP id y10so4962924lay.0 for ; Thu, 09 Apr 2015 21:29:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=uOKskOG/Q2Cn3dHFDbxGJo9RzqDKiHEXtH34o+Wckvw=; b=Qx81XmI2pT7aJXPB8A+3NpTdCAUaO0px65uJmTrgbH2AkSYmB6sMygNHK56QsKAG2i ITzSb1nb1KJNH6OqxBzcxtgxSAGyqknrDVL+YwkZWlMkQO74XvGOyxYXFmmh17h/FgSZ R16J9n6KXNooSLUYk3bTVV3hE0DgJS018RlCYmrkxGV5AVD18C/Q5kWJpTDUc6lth9+o v25RfevAsSHNr/odf4cfs33zD/Ms7Ir+sggMZ++rwlvrxNuoX75gz1JIi2o5cl6vLUt3 9VIAYaTszPmKu4B+u4I2eBJGFzvUNNp5hM8aDCDIdp0nvOl6s18McJuw1LKwfFd8o5Ch 8KfA== X-Gm-Message-State: ALoCoQknxMV2ix7fGYPMqQytu2G0KG6j2t1mMW6n+BZbns2RQgX8BfwXs/h+kNmx7YVGqah6exCD X-Received: by 10.152.23.99 with SMTP id l3mr7454013laf.61.1428640179552; Thu, 09 Apr 2015 21:29:39 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id bj2sm166318lbc.43.2015.04.09.21.29.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 21:29:38 -0700 (PDT) Date: Fri, 10 Apr 2015 06:29:35 +0200 From: Magnus Therning To: mirageos-devel Message-ID: <20150410042935.GA27321@tatooine> References: <20150409201853.GA11002@tatooine> MIME-Version: 1.0 In-Reply-To: <20150409201853.GA11002@tatooine> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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="===============1354735230147095097==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1354735230147095097== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: [...] >=20 > It works fine in Unix mode, both on x86 and on my cubietruck board. > When built in Xen mode though it doesn't work as well. >=20 > When run in Unix mode I see the expected behaviour: >=20 > shell my server console > ----- ----------------- > % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 > udp: 6 - hello >=20 > % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 > hello 6 - hello >=20 > % echo foobar | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 > foobar 6 - foobar That last line should of course read foobar 7 - foobar That was caused by a copy-paste mistake of mine. > When running the server in a VM on ARM I see the same behaviour for > UDP, but for TCP it changes. >=20 > shell my server console > ----- ----------------- > % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 > udp: 6 - hello >=20 > % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 > 6 - > 6 - And here there are even more copy-paste mistakes. I must have been tired yesterday. Just disregard the `localhost` and `127.0.0.1`, that should of course be the IPs of my cubietruck and my PC, respectively. I did a little bit more testing of this just now, and found something surprising. This is against a VM on ARM: ~~~ % echo thisisalongerstring | ncat -4 192.168.0.33 18080 alongerstring -> tcp: 192.168.0.11:48731 6 -=20 14 - alongerstring ~~~ and ~~~ % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 18080 alongerstringandthisislongerstill -> tcp: 192.168.0.11:48732 6 -=20 34 - alongerstringandthisislongerstill ~~~ and if I send a string that is shorter than 6 characters (I'm guessing including the trailing \r\n), then `ncat` hangs and on the ARM I only see a single line of "length - content": ~~~ tcp: 192.168.0.11:48766 6 - ~~~ I do wonder where those initial 6 characters go... /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus "Sendmail" and "make" are two well known programs that are pretty widely regarded as being debugged into existence. That's why their command languages are so poorly thought out and difficult to learn. It's not just you -- everyone finds them troublesome. -- Peter van der Linden, Expert C Programming, p. 220 --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUnUa8ACgkQiMWTaatN+6RIygCfaTAgMSHGUUJ6D22mDEN8pXad ZygAnRrQEz14/xa2PMfYDelfy/qiEs/7 =/B/y -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- --===============1354735230147095097== 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 --===============1354735230147095097==-- From mirageos-devel-bounces@lists.xenproject.org Fri Apr 10 05:39:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 05:39: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 1YgReo-0008Ao-VJ; Fri, 10 Apr 2015 05:39:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgRen-00087n-U3 for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 05:39:10 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id 22/B2-03284-DF167255; Fri, 10 Apr 2015 05:39:09 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-5.tower-206.messagelabs.com!1428644348!14859594!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22992 invoked from network); 10 Apr 2015 05:39:08 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Apr 2015 05:39:08 -0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7C5CE20BDA for ; Fri, 10 Apr 2015 01:39:03 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute5.internal (MEProxy); Fri, 10 Apr 2015 01:39:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=h64yxZj5omlpy557cpMHyiglXYc=; b=dINW4U IfB+soZLr58jk+p+KTZVjCHI75+J2HsoPP+wOtqK1RZYdPNRstunH0uEc9HWtP47 0kcrUn224iELN/fwmTW/UImNGnkJCHDRPT5uJffKutR8tT5UDDEHQAKr1nlEoJrL L0bbL3cMvEbdZA9EEf89X3+BcPwvVh3ikNm08= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=h64yxZj5omlpy55 7cpMHyiglXYc=; b=pf5LLgMih7/t1hOlQEVos/9S+rv46zDQmS+hcg+ttTiY1b6 sk9gh31opZoy/GotxF1EuEosYOyonAzzhvPP+JUNVAEyQU8rfot1JSEVAtSsH2sP ez10ZEvElDgM8Pg430JR3TgQ/iMaT+pe/2xP3qur+wtvGN733iejSROqKOnQ= Received: by web1.nyi.internal (Postfix, from userid 99) id 56E92AEB046; Fri, 10 Apr 2015 01:39:07 -0400 (EDT) Message-Id: <1428644347.1529046.251573169.77B894FF@webmail.messagingengine.com> X-Sasl-Enc: I/ZT8F9TF742wE1C+h4Y2N0zHzlr6B7JNHGWcbEexEal 1428644347 From: Magnus Skjegstad To: Mindy , Thomas Gazagnaire MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-0b3c2300 Date: Fri, 10 Apr 2015 06:39:07 +0100 In-Reply-To: <5526F1A8.7040203@somerandomidiot.com> References: <5526B66C.2000601@somerandomidiot.com> <5526F1A8.7040203@somerandomidiot.com> Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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 Thu, 9 Apr 2015, at 22:39, Mindy wrote: > > On 04/09/2015 07:30 PM, Thomas Gazagnaire wrote: > >> I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. > >> > >> Thanks for your consideration and support. :) > > That's awesome! Yes - very cool! > > I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? > Yes, it should work this way (once there's more code in place). > > If yes, a good way to stress test the system is to (1) generate a big history of stuff and (2) use git reset --hard to revert to arbitrary points in the past (which are supposed to be consistent) and check that nothing breaks badly (this is a good test for intermediate caches for instances). In a distributed settings, if you keep track of the state of multiple unikernels, you can try to verify that global invariants (involving multiple unikernels) still hold. > Ah, that's a good suggestion. Thank you! > > > > Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) > I'd been thinking about (or maybe remembered talking about with someone > else?) pre-seeding newly booted unikernels with caches reflecting the > current state of the local network, which is a less general case of what > you propose. One use case for this could be to let something that manages unikernels (e.g. Jitsu) update ARP tables in running unikernels. Jitsu already knows the MAC address and IP of all the unikernels it controls, so it could keep the tables up to date automatically and add/remove entries as unikernels are booted/destroyed. This could also potentially reduce the unikernel boot time if we can add ARP entries for gateways etc in advance. Magnus _______________________________________________ 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 Apr 10 05:39:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 05:39: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 1YgReo-0008Ao-VJ; Fri, 10 Apr 2015 05:39:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgRen-00087n-U3 for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 05:39:10 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id 22/B2-03284-DF167255; Fri, 10 Apr 2015 05:39:09 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-5.tower-206.messagelabs.com!1428644348!14859594!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22992 invoked from network); 10 Apr 2015 05:39:08 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Apr 2015 05:39:08 -0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7C5CE20BDA for ; Fri, 10 Apr 2015 01:39:03 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute5.internal (MEProxy); Fri, 10 Apr 2015 01:39:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=h64yxZj5omlpy557cpMHyiglXYc=; b=dINW4U IfB+soZLr58jk+p+KTZVjCHI75+J2HsoPP+wOtqK1RZYdPNRstunH0uEc9HWtP47 0kcrUn224iELN/fwmTW/UImNGnkJCHDRPT5uJffKutR8tT5UDDEHQAKr1nlEoJrL L0bbL3cMvEbdZA9EEf89X3+BcPwvVh3ikNm08= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=h64yxZj5omlpy55 7cpMHyiglXYc=; b=pf5LLgMih7/t1hOlQEVos/9S+rv46zDQmS+hcg+ttTiY1b6 sk9gh31opZoy/GotxF1EuEosYOyonAzzhvPP+JUNVAEyQU8rfot1JSEVAtSsH2sP ez10ZEvElDgM8Pg430JR3TgQ/iMaT+pe/2xP3qur+wtvGN733iejSROqKOnQ= Received: by web1.nyi.internal (Postfix, from userid 99) id 56E92AEB046; Fri, 10 Apr 2015 01:39:07 -0400 (EDT) Message-Id: <1428644347.1529046.251573169.77B894FF@webmail.messagingengine.com> X-Sasl-Enc: I/ZT8F9TF742wE1C+h4Y2N0zHzlr6B7JNHGWcbEexEal 1428644347 From: Magnus Skjegstad To: Mindy , Thomas Gazagnaire MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-0b3c2300 Date: Fri, 10 Apr 2015 06:39:07 +0100 In-Reply-To: <5526F1A8.7040203@somerandomidiot.com> References: <5526B66C.2000601@somerandomidiot.com> <5526F1A8.7040203@somerandomidiot.com> Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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 Thu, 9 Apr 2015, at 22:39, Mindy wrote: > > On 04/09/2015 07:30 PM, Thomas Gazagnaire wrote: > >> I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. > >> > >> Thanks for your consideration and support. :) > > That's awesome! Yes - very cool! > > I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? > Yes, it should work this way (once there's more code in place). > > If yes, a good way to stress test the system is to (1) generate a big history of stuff and (2) use git reset --hard to revert to arbitrary points in the past (which are supposed to be consistent) and check that nothing breaks badly (this is a good test for intermediate caches for instances). In a distributed settings, if you keep track of the state of multiple unikernels, you can try to verify that global invariants (involving multiple unikernels) still hold. > Ah, that's a good suggestion. Thank you! > > > > Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) > I'd been thinking about (or maybe remembered talking about with someone > else?) pre-seeding newly booted unikernels with caches reflecting the > current state of the local network, which is a less general case of what > you propose. One use case for this could be to let something that manages unikernels (e.g. Jitsu) update ARP tables in running unikernels. Jitsu already knows the MAC address and IP of all the unikernels it controls, so it could keep the tables up to date automatically and add/remove entries as unikernels are booted/destroyed. This could also potentially reduce the unikernel boot time if we can add ARP entries for gateways etc in advance. Magnus _______________________________________________ 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 Apr 10 11:26:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 11:26: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 1YgX4e-0004Rn-1J; Fri, 10 Apr 2015 11:26:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgX4c-0004Rg-Ep for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 11:26:10 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 25/F0-11242-153B7255; Fri, 10 Apr 2015 11:26:09 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1428665168!15307998!1 X-Originating-IP: [157.55.2.32] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31288 invoked from network); 10 Apr 2015 11:26:08 -0000 Received: from dub004-omc3s23.hotmail.com (HELO DUB004-OMC3S23.hotmail.com) (157.55.2.32) by server-10.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 10 Apr 2015 11:26:08 -0000 Received: from DUB128-W64 ([157.55.2.9]) by DUB004-OMC3S23.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Fri, 10 Apr 2015 04:26:08 -0700 X-TMN: [bTLMC37EHU0L4BNvDfbO6m54Dcqrxn9U] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Fri, 10 Apr 2015 11:26:06 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 10 Apr 2015 11:26:08.0075 (UTC) FILETIME=[23B479B0:01D07381] Subject: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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="===============4367188529973261112==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4367188529973261112== Content-Type: multipart/alternative; boundary="_571883b7-6b12-4c31-a789-b4d7bc551761_" --_571883b7-6b12-4c31-a789-b4d7bc551761_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've just received a Cubieboard4 and I'm trying to work out what's needed t= o add it to blobs.openmirage.org. Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd=2C there are two sec= tions which differ: 1. The address locations: kernel=2C ramdisk etc. 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. Does anyone have any idea on where to derive the (1)? The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dt= s & sun9i-a80.dtsi). Also=2C is there anything else I've missed and need to take care of? - n = --_571883b7-6b12-4c31-a789-b4d7bc551761_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've just received a Cubieboard4= and I'm trying to work out what's needed to add it to blobs.openmirage.org= .

Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd=2C there ar= e two sections which differ:

1. The address locations: kernel=2C ram= disk etc.
2. The sun7i-a20-cubieboard2/cubietruck.dtb files.

Does= anyone have any idea on where to derive the (1)?

The dtb file I can= create from the linaro 15.X branch (sun9i-a80-optimus.dts &=3B sun9i-a8= 0.dtsi).

Also=2C is there anything else I've missed and need to take= care of?

- n


= --_571883b7-6b12-4c31-a789-b4d7bc551761_-- --===============4367188529973261112== 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 --===============4367188529973261112==-- From mirageos-devel-bounces@lists.xenproject.org Fri Apr 10 11:26:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 11:26: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 1YgX4e-0004Rn-1J; Fri, 10 Apr 2015 11:26:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgX4c-0004Rg-Ep for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 11:26:10 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 25/F0-11242-153B7255; Fri, 10 Apr 2015 11:26:09 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1428665168!15307998!1 X-Originating-IP: [157.55.2.32] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31288 invoked from network); 10 Apr 2015 11:26:08 -0000 Received: from dub004-omc3s23.hotmail.com (HELO DUB004-OMC3S23.hotmail.com) (157.55.2.32) by server-10.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 10 Apr 2015 11:26:08 -0000 Received: from DUB128-W64 ([157.55.2.9]) by DUB004-OMC3S23.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Fri, 10 Apr 2015 04:26:08 -0700 X-TMN: [bTLMC37EHU0L4BNvDfbO6m54Dcqrxn9U] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Fri, 10 Apr 2015 11:26:06 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 10 Apr 2015 11:26:08.0075 (UTC) FILETIME=[23B479B0:01D07381] Subject: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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="===============4367188529973261112==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4367188529973261112== Content-Type: multipart/alternative; boundary="_571883b7-6b12-4c31-a789-b4d7bc551761_" --_571883b7-6b12-4c31-a789-b4d7bc551761_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've just received a Cubieboard4 and I'm trying to work out what's needed t= o add it to blobs.openmirage.org. Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd=2C there are two sec= tions which differ: 1. The address locations: kernel=2C ramdisk etc. 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. Does anyone have any idea on where to derive the (1)? The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dt= s & sun9i-a80.dtsi). Also=2C is there anything else I've missed and need to take care of? - n = --_571883b7-6b12-4c31-a789-b4d7bc551761_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've just received a Cubieboard4= and I'm trying to work out what's needed to add it to blobs.openmirage.org= .

Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd=2C there ar= e two sections which differ:

1. The address locations: kernel=2C ram= disk etc.
2. The sun7i-a20-cubieboard2/cubietruck.dtb files.

Does= anyone have any idea on where to derive the (1)?

The dtb file I can= create from the linaro 15.X branch (sun9i-a80-optimus.dts &=3B sun9i-a8= 0.dtsi).

Also=2C is there anything else I've missed and need to take= care of?

- n


= --_571883b7-6b12-4c31-a789-b4d7bc551761_-- --===============4367188529973261112== 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 --===============4367188529973261112==-- From mirageos-devel-bounces@lists.xenproject.org Fri Apr 10 16:28:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 16:28: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 1Ygbn7-0003Kw-Gx; Fri, 10 Apr 2015 16:28:25 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ygbn5-0003Kr-Qb for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 16:28:23 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id 06/CA-06072-72AF7255; Fri, 10 Apr 2015 16:28:23 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1428683301!17077685!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12197 invoked from network); 10 Apr 2015 16:28:22 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2015 16:28:22 -0000 Received: by labbd9 with SMTP id bd9so17027017lab.2 for ; Fri, 10 Apr 2015 09:28:21 -0700 (PDT) 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=2TkSY2BMpTSs6Qgwhvw+RRCa7OulW8i8MzhoWITg+eo=; b=YodEkJBOgZG8ftPzyKcuCkKNUiTPRXJupbNi/FFCvOHWVgYq9pMX8hSq7w5D8djNRp Ypg8sCnVcYoT9i0c5Wkoe40kXbMJQOqqnRbOGSGVO6iCWdEeOrZVAEKqgchq+6LBtB4L HSbliaxhpdhCTOG/KMJLkfXpIUu9rMtQHctzuM0imr6vYnmLEduBmtq/Ku+RmxHFw+pe cpO+SPVxyvBZzY3iZiYYJmG7kQTb/Gq5NbAOqfydUgNXE820EQWLBpqoZHqWnu/q+YPP uiNtyRNYQfESy5uRlmDclHt1GFmg3G4GD4cz0UY2TEu5Ehc2NbZ7Cw29hVozzSWss1AG jJcg== MIME-Version: 1.0 X-Received: by 10.152.44.161 with SMTP id f1mr2159553lam.26.1428683301500; Fri, 10 Apr 2015 09:28:21 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Fri, 10 Apr 2015 09:28:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Apr 2015 17:28:21 +0100 Message-ID: From: Thomas Leonard To: Nick Betteridge Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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 April 2015 at 12:26, Nick Betteridge wrote: > I've just received a Cubieboard4 and I'm trying to work out what's needed to > add it to blobs.openmirage.org. > > Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd, there are two > sections which differ: > > 1. The address locations: kernel, ramdisk etc. > 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. > > Does anyone have any idea on where to derive the (1)? I got the original information from here: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner I think the CB4 has the same amount of memory as the CB3, so it might be fine as-is. > The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dts > & sun9i-a80.dtsi). > > Also, is there anything else I've missed and need to take care of? -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 10 16:28:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 16:28: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 1Ygbn7-0003Kw-Gx; Fri, 10 Apr 2015 16:28:25 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ygbn5-0003Kr-Qb for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 16:28:23 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id 06/CA-06072-72AF7255; Fri, 10 Apr 2015 16:28:23 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1428683301!17077685!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12197 invoked from network); 10 Apr 2015 16:28:22 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2015 16:28:22 -0000 Received: by labbd9 with SMTP id bd9so17027017lab.2 for ; Fri, 10 Apr 2015 09:28:21 -0700 (PDT) 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=2TkSY2BMpTSs6Qgwhvw+RRCa7OulW8i8MzhoWITg+eo=; b=YodEkJBOgZG8ftPzyKcuCkKNUiTPRXJupbNi/FFCvOHWVgYq9pMX8hSq7w5D8djNRp Ypg8sCnVcYoT9i0c5Wkoe40kXbMJQOqqnRbOGSGVO6iCWdEeOrZVAEKqgchq+6LBtB4L HSbliaxhpdhCTOG/KMJLkfXpIUu9rMtQHctzuM0imr6vYnmLEduBmtq/Ku+RmxHFw+pe cpO+SPVxyvBZzY3iZiYYJmG7kQTb/Gq5NbAOqfydUgNXE820EQWLBpqoZHqWnu/q+YPP uiNtyRNYQfESy5uRlmDclHt1GFmg3G4GD4cz0UY2TEu5Ehc2NbZ7Cw29hVozzSWss1AG jJcg== MIME-Version: 1.0 X-Received: by 10.152.44.161 with SMTP id f1mr2159553lam.26.1428683301500; Fri, 10 Apr 2015 09:28:21 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Fri, 10 Apr 2015 09:28:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Apr 2015 17:28:21 +0100 Message-ID: From: Thomas Leonard To: Nick Betteridge Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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 April 2015 at 12:26, Nick Betteridge wrote: > I've just received a Cubieboard4 and I'm trying to work out what's needed to > add it to blobs.openmirage.org. > > Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd, there are two > sections which differ: > > 1. The address locations: kernel, ramdisk etc. > 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. > > Does anyone have any idea on where to derive the (1)? I got the original information from here: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner I think the CB4 has the same amount of memory as the CB3, so it might be fine as-is. > The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dts > & sun9i-a80.dtsi). > > Also, is there anything else I've missed and need to take care of? -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 10 16:44:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 16:44: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 1Ygc2V-000513-NB; Fri, 10 Apr 2015 16:44:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ygc2U-00050y-DN for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 16:44:18 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id 11/F0-13265-EDDF7255; Fri, 10 Apr 2015 16:44:14 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1428684253!15291232!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19983 invoked from network); 10 Apr 2015 16:44:13 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2015 16:44:13 -0000 Received: by lbbqq2 with SMTP id qq2so17833888lbb.3 for ; Fri, 10 Apr 2015 09:44:13 -0700 (PDT) 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=krWP+CG/JlJzoDKfB6RhCUna6LtuUOhDtdQIq2bz3NA=; b=PkiNdgywjXX3QYoTfWo7QLSLZyjA8GGt+eRZGQ8e4WeJKJukQK7J/xbtoaoBezZuqf /JzoUOzqSj6yu6gPiRuuoD3l4qNi3hom/6QsugaKpiYbOI7gEM1gqrXkkTnUY/uBJFWb c86rWnM7iFHKU7p0aTPAVTHlONVOBM+Z68vBtHa9SWlRTM5LX5Jen8zN/7GDJGsgdvfS oAabg1uenP+SyvJN4efg1GpH44W+PqC2gzxd/JJPz2xzs5x8AvY8SbmSGChVEbBVEK+b EDp5/fj9qO7qjhFNbsUmHsC17l3pi58qS3qz0HbYYFj3xSVNYfA4acn4mxL4rDPuSV4u ymHw== MIME-Version: 1.0 X-Received: by 10.112.13.73 with SMTP id f9mr2244564lbc.124.1428684252731; Fri, 10 Apr 2015 09:44:12 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Fri, 10 Apr 2015 09:44:12 -0700 (PDT) In-Reply-To: <20150410042935.GA27321@tatooine> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> Date: Fri, 10 Apr 2015 17:44:12 +0100 Message-ID: From: Thomas Leonard To: Magnus Therning Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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 April 2015 at 05:29, Magnus Therning wrote: > On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: > [...] > >> >> It works fine in Unix mode, both on x86 and on my cubietruck board. >> When built in Xen mode though it doesn't work as well. >> >> When run in Unix mode I see the expected behaviour: >> >> shell my server console >> ----- ----------------- >> % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 >> udp: 6 - hello >> >> % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 >> hello 6 - hello >> >> % echo foobar | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 >> foobar 6 - foobar > > That last line should of course read > > foobar 7 - foobar > > That was caused by a copy-paste mistake of mine. > >> When running the server in a VM on ARM I see the same behaviour for >> UDP, but for TCP it changes. >> >> shell my server console >> ----- ----------------- >> % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 >> udp: 6 - hello >> >> % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 >> 6 - >> 6 - > > And here there are even more copy-paste mistakes. I must have been > tired yesterday. Just disregard the `localhost` and `127.0.0.1`, that > should of course be the IPs of my cubietruck and my PC, respectively. > > I did a little bit more testing of this just now, and found something > surprising. This is against a VM on ARM: > > ~~~ > % echo thisisalongerstring | ncat -4 192.168.0.33 18080 > alongerstring > > -> > > tcp: 192.168.0.11:48731 > 6 - > 14 - alongerstring > ~~~ > > and > > ~~~ > % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 18080 > alongerstringandthisislongerstill > > -> > > tcp: 192.168.0.11:48732 > 6 - > 34 - alongerstringandthisislongerstill > ~~~ > > and if I send a string that is shorter than 6 characters (I'm guessing > including the trailing \r\n), then `ncat` hangs and on the ARM I only > see a single line of "length - content": > > ~~~ > tcp: 192.168.0.11:48766 > 6 - > ~~~ > > I do wonder where those initial 6 characters go... Interesting! Probably the easiest thing now is to git clone mirage-net-xen and/or mirage-tcpip and add some code to dump out the buffer at various points: https://github.com/mirage/mirage-net-xen/ https://github.com/mirage/mirage-tcpip/ (use e.g. "opam pin add tcpip mirage-tcpip" to rebuild with your debug version, then make clean and rebuild your unikernel) I think this is the first point where we learn that Xen has placed the new packet in our buffer: https://github.com/mirage/mirage-net-xen/blob/541e86f53cb8cf426aabdd7f090779fc5ea9fe93/lib/netif.ml#L387 A few Cstruct.hexdump calls along the way should let you see where it first differs from the wireshare capture (assuming that looks OK). -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 10 16:44:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 10 Apr 2015 16:44: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 1Ygc2V-000513-NB; Fri, 10 Apr 2015 16:44:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ygc2U-00050y-DN for mirageos-devel@lists.xenproject.org; Fri, 10 Apr 2015 16:44:18 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id 11/F0-13265-EDDF7255; Fri, 10 Apr 2015 16:44:14 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1428684253!15291232!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19983 invoked from network); 10 Apr 2015 16:44:13 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2015 16:44:13 -0000 Received: by lbbqq2 with SMTP id qq2so17833888lbb.3 for ; Fri, 10 Apr 2015 09:44:13 -0700 (PDT) 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=krWP+CG/JlJzoDKfB6RhCUna6LtuUOhDtdQIq2bz3NA=; b=PkiNdgywjXX3QYoTfWo7QLSLZyjA8GGt+eRZGQ8e4WeJKJukQK7J/xbtoaoBezZuqf /JzoUOzqSj6yu6gPiRuuoD3l4qNi3hom/6QsugaKpiYbOI7gEM1gqrXkkTnUY/uBJFWb c86rWnM7iFHKU7p0aTPAVTHlONVOBM+Z68vBtHa9SWlRTM5LX5Jen8zN/7GDJGsgdvfS oAabg1uenP+SyvJN4efg1GpH44W+PqC2gzxd/JJPz2xzs5x8AvY8SbmSGChVEbBVEK+b EDp5/fj9qO7qjhFNbsUmHsC17l3pi58qS3qz0HbYYFj3xSVNYfA4acn4mxL4rDPuSV4u ymHw== MIME-Version: 1.0 X-Received: by 10.112.13.73 with SMTP id f9mr2244564lbc.124.1428684252731; Fri, 10 Apr 2015 09:44:12 -0700 (PDT) Received: by 10.25.207.17 with HTTP; Fri, 10 Apr 2015 09:44:12 -0700 (PDT) In-Reply-To: <20150410042935.GA27321@tatooine> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> Date: Fri, 10 Apr 2015 17:44:12 +0100 Message-ID: From: Thomas Leonard To: Magnus Therning Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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 April 2015 at 05:29, Magnus Therning wrote: > On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: > [...] > >> >> It works fine in Unix mode, both on x86 and on my cubietruck board. >> When built in Xen mode though it doesn't work as well. >> >> When run in Unix mode I see the expected behaviour: >> >> shell my server console >> ----- ----------------- >> % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 >> udp: 6 - hello >> >> % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 >> hello 6 - hello >> >> % echo foobar | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 >> foobar 6 - foobar > > That last line should of course read > > foobar 7 - foobar > > That was caused by a copy-paste mistake of mine. > >> When running the server in a VM on ARM I see the same behaviour for >> UDP, but for TCP it changes. >> >> shell my server console >> ----- ----------------- >> % echo hello | ncat -4 -u localhost 18081 -> udp: 127.0.0.1:46507 >> udp: 6 - hello >> >> % echo hello | ncat -4 localhost 18080 -> tcp: 127.0.0.1:59888 >> 6 - >> 6 - > > And here there are even more copy-paste mistakes. I must have been > tired yesterday. Just disregard the `localhost` and `127.0.0.1`, that > should of course be the IPs of my cubietruck and my PC, respectively. > > I did a little bit more testing of this just now, and found something > surprising. This is against a VM on ARM: > > ~~~ > % echo thisisalongerstring | ncat -4 192.168.0.33 18080 > alongerstring > > -> > > tcp: 192.168.0.11:48731 > 6 - > 14 - alongerstring > ~~~ > > and > > ~~~ > % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 18080 > alongerstringandthisislongerstill > > -> > > tcp: 192.168.0.11:48732 > 6 - > 34 - alongerstringandthisislongerstill > ~~~ > > and if I send a string that is shorter than 6 characters (I'm guessing > including the trailing \r\n), then `ncat` hangs and on the ARM I only > see a single line of "length - content": > > ~~~ > tcp: 192.168.0.11:48766 > 6 - > ~~~ > > I do wonder where those initial 6 characters go... Interesting! Probably the easiest thing now is to git clone mirage-net-xen and/or mirage-tcpip and add some code to dump out the buffer at various points: https://github.com/mirage/mirage-net-xen/ https://github.com/mirage/mirage-tcpip/ (use e.g. "opam pin add tcpip mirage-tcpip" to rebuild with your debug version, then make clean and rebuild your unikernel) I think this is the first point where we learn that Xen has placed the new packet in our buffer: https://github.com/mirage/mirage-net-xen/blob/541e86f53cb8cf426aabdd7f090779fc5ea9fe93/lib/netif.ml#L387 A few Cstruct.hexdump calls along the way should let you see where it first differs from the wireshare capture (assuming that looks OK). -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 11 15:14:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 11 Apr 2015 15:14: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 1Ygx6Y-00075D-GW; Sat, 11 Apr 2015 15:13:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ygx6W-000758-Tx for mirageos-devel@lists.xenproject.org; Sat, 11 Apr 2015 15:13:53 +0000 Received: from [85.158.139.211] by server-13.bemta-5.messagelabs.com id 02/D4-08090-03A39255; Sat, 11 Apr 2015 15:13:52 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-6.tower-206.messagelabs.com!1428765230!15194306!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9714 invoked from network); 11 Apr 2015 15:13:51 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Apr 2015 15:13:51 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3A95720887 for ; Sat, 11 Apr 2015 11:13:46 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute6.internal (MEProxy); Sat, 11 Apr 2015 11:13:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=83J86vaYdj+4QRXZpk0AYBhugQs=; b=OTZCno 6LP2QOGDkuVlBpekzjlsVPA8Li3a9QyOqy7dM9RqZGsQeDKHPp5fioGGUhl1sZDL xNMYViN5ATWAWr7g5cpuR35fqPVVyfj8EpuQ4wgo3hRPzLgDY6p1osKhKGCbZr/V qlkcGxaP7t8olBbs/J0zAUFYql/FmwG5mqjbM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=83J86vaYdj+4QRX Zpk0AYBhugQs=; b=sXh2qlkuj3AuTqqsfZhYDYuCJ7fL+niJTxMsZ6Q8c+Mjtq6 g2xWYkRJiJpN8KKywbbP9LVuUWydEACBl/46Sy72p5oe3+BBKXTIXDtEgmbU7Ew9 bl7mYz+fE6qIhuJvEoCxgsX1G3KmDQ+tVgbkeM7R9lPG2tw7e1q4+Ir6nNsc= Received: by web1.nyi.internal (Postfix, from userid 99) id 29FDEAECAD7; Sat, 11 Apr 2015 11:13:50 -0400 (EDT) Message-Id: <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> X-Sasl-Enc: S6h5P72oZBUpIIimaw9kXGfoSnWgHq3ovV0ZovkAlwv0 1428765230 From: Magnus Skjegstad To: Magnus Therning , "mirageos-devel" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-0b3c2300 In-Reply-To: <20150410042935.GA27321@tatooine> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> Date: Sat, 11 Apr 2015 16:13:50 +0100 Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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, 10 Apr 2015, at 05:29, Magnus Therning wrote: > On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: > [...] > I did a little bit more testing of this just now, and found something > surprising. This is against a VM on ARM: > > ~~~ > % echo thisisalongerstring | ncat -4 192.168.0.33 18080 > alongerstring > > -> > > tcp: 192.168.0.11:48731 > 6 - > 14 - alongerstring > ~~~ > > and > > ~~~ > % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 > 18080 > alongerstringandthisislongerstill > > -> > > tcp: 192.168.0.11:48732 > 6 - > 34 - alongerstringandthisislongerstill > ~~~ > > and if I send a string that is shorter than 6 characters (I'm guessing > including the trailing \r\n), then `ncat` hangs and on the ARM I only > see a single line of "length - content": > > ~~~ > tcp: 192.168.0.11:48766 > 6 - > ~~~ > > I do wonder where those initial 6 characters go... > Hm - I am able to reproduce this. I have a cubieboard and an x86 Xen server connected to the same switch. If I run the unikernel above on the x86 server I can access it remotely and from dom0 without problems. It also works fine if I run the unikernel in Xen on the cubieboard and try to access it from dom0: Shell: $ echo 'thisisalongstring' | ncat -4 10.0.1.24 18080 thisisalongstring $ Unikernel console: tcp: 10.0.1.10:37663 18 - thisisalongstring However, if I try to access the unikernel on the cubieboard remotely from the x86 server: Shell: $ echo 'thisisalongstring' | ncat -4 10.0.1.24 18080 alongstring ^C Unikernel console: tcp: 10.0.1.9:58213 6 - 12 - alongstring Shell: $ echo hello | ncat -4 10.0.1.24 18080 $ Unikernel console: tcp: 10.0.1.9:58214 6 - 6 - tcpdump -ni on the vif on the cubieboard shows the following during the failed connection: 14:19:04.460636 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [S], seq 53068681, win 29200, options [mss 1460,sackOK,TS val 69443464 ecr 0,nop,wscale 7], length 0 14:19:04.461292 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [S.], seq 452856959, ack 53068682, win 65535, options [mss 1460,wscale 2,eol], length 0 14:19:04.461555 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 1, win 229, length 0 14:19:04.461808 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [P.], seq 1:19, ack 1, win 229, length 18 14:19:04.461838 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [F.], seq 19, ack 1, win 229, length 0 14:19:04.462176 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [P.], seq 1:7, ack 7, win 65535, length 6 14:19:04.462242 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.462430 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 7, win 229, length 0 14:19:04.463034 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.463068 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.463099 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.664534 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 7, win 229, length 12 14:19:04.665234 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [P.], seq 7:19, ack 26, win 65535, length 12 14:19:04.665325 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [P.], seq 19:25, ack 26, win 65535, length 6 14:19:04.665358 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:04.665647 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 19, win 229, length 0 14:19:04.665671 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 25, win 229, length 0 14:19:04.666333 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:04.666373 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:05.072495 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:05.073073 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:05.888468 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:05.889067 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:07.524471 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:07.525057 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:10.796388 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:10.797008 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:17.340268 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:17.340894 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:30.411981 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:30.412582 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 [...] I am using tcpip 2.3.1 and mirage-net-xen 1.4.1. Magnus _______________________________________________ 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 Apr 11 15:14:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 11 Apr 2015 15:14: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 1Ygx6Y-00075D-GW; Sat, 11 Apr 2015 15:13:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ygx6W-000758-Tx for mirageos-devel@lists.xenproject.org; Sat, 11 Apr 2015 15:13:53 +0000 Received: from [85.158.139.211] by server-13.bemta-5.messagelabs.com id 02/D4-08090-03A39255; Sat, 11 Apr 2015 15:13:52 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-6.tower-206.messagelabs.com!1428765230!15194306!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9714 invoked from network); 11 Apr 2015 15:13:51 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Apr 2015 15:13:51 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3A95720887 for ; Sat, 11 Apr 2015 11:13:46 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute6.internal (MEProxy); Sat, 11 Apr 2015 11:13:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=83J86vaYdj+4QRXZpk0AYBhugQs=; b=OTZCno 6LP2QOGDkuVlBpekzjlsVPA8Li3a9QyOqy7dM9RqZGsQeDKHPp5fioGGUhl1sZDL xNMYViN5ATWAWr7g5cpuR35fqPVVyfj8EpuQ4wgo3hRPzLgDY6p1osKhKGCbZr/V qlkcGxaP7t8olBbs/J0zAUFYql/FmwG5mqjbM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=83J86vaYdj+4QRX Zpk0AYBhugQs=; b=sXh2qlkuj3AuTqqsfZhYDYuCJ7fL+niJTxMsZ6Q8c+Mjtq6 g2xWYkRJiJpN8KKywbbP9LVuUWydEACBl/46Sy72p5oe3+BBKXTIXDtEgmbU7Ew9 bl7mYz+fE6qIhuJvEoCxgsX1G3KmDQ+tVgbkeM7R9lPG2tw7e1q4+Ir6nNsc= Received: by web1.nyi.internal (Postfix, from userid 99) id 29FDEAECAD7; Sat, 11 Apr 2015 11:13:50 -0400 (EDT) Message-Id: <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> X-Sasl-Enc: S6h5P72oZBUpIIimaw9kXGfoSnWgHq3ovV0ZovkAlwv0 1428765230 From: Magnus Skjegstad To: Magnus Therning , "mirageos-devel" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-0b3c2300 In-Reply-To: <20150410042935.GA27321@tatooine> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> Date: Sat, 11 Apr 2015 16:13:50 +0100 Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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, 10 Apr 2015, at 05:29, Magnus Therning wrote: > On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: > [...] > I did a little bit more testing of this just now, and found something > surprising. This is against a VM on ARM: > > ~~~ > % echo thisisalongerstring | ncat -4 192.168.0.33 18080 > alongerstring > > -> > > tcp: 192.168.0.11:48731 > 6 - > 14 - alongerstring > ~~~ > > and > > ~~~ > % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 > 18080 > alongerstringandthisislongerstill > > -> > > tcp: 192.168.0.11:48732 > 6 - > 34 - alongerstringandthisislongerstill > ~~~ > > and if I send a string that is shorter than 6 characters (I'm guessing > including the trailing \r\n), then `ncat` hangs and on the ARM I only > see a single line of "length - content": > > ~~~ > tcp: 192.168.0.11:48766 > 6 - > ~~~ > > I do wonder where those initial 6 characters go... > Hm - I am able to reproduce this. I have a cubieboard and an x86 Xen server connected to the same switch. If I run the unikernel above on the x86 server I can access it remotely and from dom0 without problems. It also works fine if I run the unikernel in Xen on the cubieboard and try to access it from dom0: Shell: $ echo 'thisisalongstring' | ncat -4 10.0.1.24 18080 thisisalongstring $ Unikernel console: tcp: 10.0.1.10:37663 18 - thisisalongstring However, if I try to access the unikernel on the cubieboard remotely from the x86 server: Shell: $ echo 'thisisalongstring' | ncat -4 10.0.1.24 18080 alongstring ^C Unikernel console: tcp: 10.0.1.9:58213 6 - 12 - alongstring Shell: $ echo hello | ncat -4 10.0.1.24 18080 $ Unikernel console: tcp: 10.0.1.9:58214 6 - 6 - tcpdump -ni on the vif on the cubieboard shows the following during the failed connection: 14:19:04.460636 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [S], seq 53068681, win 29200, options [mss 1460,sackOK,TS val 69443464 ecr 0,nop,wscale 7], length 0 14:19:04.461292 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [S.], seq 452856959, ack 53068682, win 65535, options [mss 1460,wscale 2,eol], length 0 14:19:04.461555 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 1, win 229, length 0 14:19:04.461808 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [P.], seq 1:19, ack 1, win 229, length 18 14:19:04.461838 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [F.], seq 19, ack 1, win 229, length 0 14:19:04.462176 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [P.], seq 1:7, ack 7, win 65535, length 6 14:19:04.462242 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.462430 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 7, win 229, length 0 14:19:04.463034 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.463068 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.463099 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 7, win 65535, length 0 14:19:04.664534 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 7, win 229, length 12 14:19:04.665234 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [P.], seq 7:19, ack 26, win 65535, length 12 14:19:04.665325 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [P.], seq 19:25, ack 26, win 65535, length 6 14:19:04.665358 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:04.665647 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 19, win 229, length 0 14:19:04.665671 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [.], ack 25, win 229, length 0 14:19:04.666333 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:04.666373 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:05.072495 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:05.073073 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:05.888468 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:05.889067 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:07.524471 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:07.525057 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:10.796388 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:10.797008 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:17.340268 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:17.340894 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 14:19:30.411981 IP 10.0.1.9.58217 > 10.0.1.24.18080: Flags [FP.], seq 7:19, ack 25, win 229, length 12 14:19:30.412582 IP 10.0.1.24.18080 > 10.0.1.9.58217: Flags [.], ack 26, win 65535, length 0 [...] I am using tcpip 2.3.1 and mirage-net-xen 1.4.1. Magnus _______________________________________________ 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 Apr 11 15:33:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 11 Apr 2015 15:33:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgxPp-0008Mq-Va; Sat, 11 Apr 2015 15:33:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgxPo-0008Ml-EV for mirageos-devel@lists.xenproject.org; Sat, 11 Apr 2015 15:33:48 +0000 Received: from [85.158.139.211] by server-7.bemta-5.messagelabs.com id 30/B4-02028-BDE39255; Sat, 11 Apr 2015 15:33:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1428766425!15196157!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30775 invoked from network); 11 Apr 2015 15:33:45 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Apr 2015 15:33:45 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 00c9f512; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 11 Apr 2015 16:33:42 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> Date: Sat, 11 Apr 2015 23:33:40 +0800 Message-Id: References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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 Apr 2015, at 23:13, Magnus Skjegstad wrote: > > On Fri, 10 Apr 2015, at 05:29, Magnus Therning wrote: >> On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: >> [...] >> I did a little bit more testing of this just now, and found something >> surprising. This is against a VM on ARM: >> >> ~~~ >> % echo thisisalongerstring | ncat -4 192.168.0.33 18080 >> alongerstring >> >> -> >> >> tcp: 192.168.0.11:48731 >> 6 - >> 14 - alongerstring >> ~~~ >> >> and >> >> ~~~ >> % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 >> 18080 >> alongerstringandthisislongerstill >> >> -> >> >> tcp: 192.168.0.11:48732 >> 6 - >> 34 - alongerstringandthisislongerstill >> ~~~ >> >> and if I send a string that is shorter than 6 characters (I'm guessing >> including the trailing \r\n), then `ncat` hangs and on the ARM I only >> see a single line of "length - content": >> >> ~~~ >> tcp: 192.168.0.11:48766 >> 6 - >> ~~~ >> >> I do wonder where those initial 6 characters go... >> > > Hm - I am able to reproduce this. I have a cubieboard and an x86 Xen > server connected to the same switch. If I run the unikernel above on the > x86 server I can access it remotely and from dom0 without problems. It > also works fine if I run the unikernel in Xen on the cubieboard and try > to access it from dom0: > > I am using tcpip 2.3.1 and mirage-net-xen 1.4.1. Can you bisect backwards a few versions to check if this goes away? I'm a few thousands miles away from my Cubies until Tuesday, so can't try this out myself. The usual culprit for such problems is TCP offload, but this sounds like more of a physical driver issue. As another datapoint, does a Linux domU VM have networking? -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 Apr 11 15:33:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 11 Apr 2015 15:33:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgxPp-0008Mq-Va; Sat, 11 Apr 2015 15:33:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YgxPo-0008Ml-EV for mirageos-devel@lists.xenproject.org; Sat, 11 Apr 2015 15:33:48 +0000 Received: from [85.158.139.211] by server-7.bemta-5.messagelabs.com id 30/B4-02028-BDE39255; Sat, 11 Apr 2015 15:33:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1428766425!15196157!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30775 invoked from network); 11 Apr 2015 15:33:45 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Apr 2015 15:33:45 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 00c9f512; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 11 Apr 2015 16:33:42 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> Date: Sat, 11 Apr 2015 23:33:40 +0800 Message-Id: References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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 Apr 2015, at 23:13, Magnus Skjegstad wrote: > > On Fri, 10 Apr 2015, at 05:29, Magnus Therning wrote: >> On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: >> [...] >> I did a little bit more testing of this just now, and found something >> surprising. This is against a VM on ARM: >> >> ~~~ >> % echo thisisalongerstring | ncat -4 192.168.0.33 18080 >> alongerstring >> >> -> >> >> tcp: 192.168.0.11:48731 >> 6 - >> 14 - alongerstring >> ~~~ >> >> and >> >> ~~~ >> % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 >> 18080 >> alongerstringandthisislongerstill >> >> -> >> >> tcp: 192.168.0.11:48732 >> 6 - >> 34 - alongerstringandthisislongerstill >> ~~~ >> >> and if I send a string that is shorter than 6 characters (I'm guessing >> including the trailing \r\n), then `ncat` hangs and on the ARM I only >> see a single line of "length - content": >> >> ~~~ >> tcp: 192.168.0.11:48766 >> 6 - >> ~~~ >> >> I do wonder where those initial 6 characters go... >> > > Hm - I am able to reproduce this. I have a cubieboard and an x86 Xen > server connected to the same switch. If I run the unikernel above on the > x86 server I can access it remotely and from dom0 without problems. It > also works fine if I run the unikernel in Xen on the cubieboard and try > to access it from dom0: > > I am using tcpip 2.3.1 and mirage-net-xen 1.4.1. Can you bisect backwards a few versions to check if this goes away? I'm a few thousands miles away from my Cubies until Tuesday, so can't try this out myself. The usual culprit for such problems is TCP offload, but this sounds like more of a physical driver issue. As another datapoint, does a Linux domU VM have networking? -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 Apr 12 04:33:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 04:33: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 1Yh9a7-0005SP-BQ; Sun, 12 Apr 2015 04:33:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yh9a5-0005SK-M2 for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 04:33:13 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 38/75-23180-885F9255; Sun, 12 Apr 2015 04:33:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1428813191!12561584!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29282 invoked from network); 12 Apr 2015 04:33:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2015 04:33:12 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 64ea5c00; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 12 Apr 2015 05:33:10 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 12 Apr 2015 12:33:00 +0800 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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 Apr 2015, at 00:28, Thomas Leonard wrote: > > On 10 April 2015 at 12:26, Nick Betteridge wrote: >> I've just received a Cubieboard4 and I'm trying to work out what's needed to >> add it to blobs.openmirage.org. >> >> Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd, there are two >> sections which differ: >> >> 1. The address locations: kernel, ramdisk etc. >> 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. >> >> Does anyone have any idea on where to derive the (1)? > > I got the original information from here: > > http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner > > I think the CB4 has the same amount of memory as the CB3, so it might > be fine as-is. > >> The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dts >> & sun9i-a80.dtsi). >> >> Also, is there anything else I've missed and need to take care of? > I've ordered one for myself as well. The extra RAM will certainly come in useful for deployments! If you have a setup with a serial cable, something else to experiment with is to upgrade the version of Xen that's supplied to Xen 4.5. The current Xen 4.4-rc had a limitation that half of the board memory can't be assigned to domUs, and I think that got fixed in Xen 4.5. Thomas, do you remember the details of this? 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 Apr 12 04:33:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 04:33: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 1Yh9a7-0005SP-BQ; Sun, 12 Apr 2015 04:33:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yh9a5-0005SK-M2 for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 04:33:13 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 38/75-23180-885F9255; Sun, 12 Apr 2015 04:33:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1428813191!12561584!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29282 invoked from network); 12 Apr 2015 04:33:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2015 04:33:12 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 64ea5c00; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 12 Apr 2015 05:33:10 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 12 Apr 2015 12:33:00 +0800 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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 Apr 2015, at 00:28, Thomas Leonard wrote: > > On 10 April 2015 at 12:26, Nick Betteridge wrote: >> I've just received a Cubieboard4 and I'm trying to work out what's needed to >> add it to blobs.openmirage.org. >> >> Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd, there are two >> sections which differ: >> >> 1. The address locations: kernel, ramdisk etc. >> 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. >> >> Does anyone have any idea on where to derive the (1)? > > I got the original information from here: > > http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner > > I think the CB4 has the same amount of memory as the CB3, so it might > be fine as-is. > >> The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dts >> & sun9i-a80.dtsi). >> >> Also, is there anything else I've missed and need to take care of? > I've ordered one for myself as well. The extra RAM will certainly come in useful for deployments! If you have a setup with a serial cable, something else to experiment with is to upgrade the version of Xen that's supplied to Xen 4.5. The current Xen 4.4-rc had a limitation that half of the board memory can't be assigned to domUs, and I think that got fixed in Xen 4.5. Thomas, do you remember the details of this? 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 Apr 12 06:14:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 06:14:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhBAM-0003IG-KM; Sun, 12 Apr 2015 06:14:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhBAM-0003IB-3g for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 06:14:46 +0000 Received: from [85.158.139.211] by server-8.bemta-5.messagelabs.com id 10/8A-19484-55D0A255; Sun, 12 Apr 2015 06:14:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-206.messagelabs.com!1428819284!15245579!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3202 invoked from network); 12 Apr 2015 06:14:44 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2015 06:14:44 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 966eafd5; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 12 Apr 2015 07:14:43 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5526F1A8.7040203@somerandomidiot.com> Date: Sun, 12 Apr 2015 14:14:36 +0800 Message-Id: <8CB2BF41-F54D-461E-9958-EF8F6440144F@recoil.org> References: <5526B66C.2000601@somerandomidiot.com> <5526F1A8.7040203@somerandomidiot.com> To: Mindy Preston X-Mailer: Apple Mail (2.2098) Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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 Apr 2015, at 05:39, Mindy wrote: > > On 04/09/2015 07:30 PM, Thomas Gazagnaire wrote: >>> I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. >>> >>> Thanks for your consideration and support. :) >> That's awesome! >> >> I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? > Yes, it should work this way (once there's more code in place). <...> >> Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) > I'd been thinking about (or maybe remembered talking about with someone else?) pre-seeding newly booted unikernels with caches reflecting the current state of the local network, which is a less general case of what you propose. That was me -- the idea is tied into the above two points I've quoted. Once you establish Irmin as a trusted communications channel between two unikernels, then you can start using it to feed in state as well. ARP broadcast is obviously a very legacy way to discover other hosts on the network, and so is one of the first places where we could start providing a migration path away from rather high-latency mechanisms such as multicast DNS and broadcast protocols, towards something that can very efficiently communicate a change of states to all other nodes. In addition to being more efficient, it's also easier to build a stronger trust model ("where did this ARP update come from? Why is it different from all the other nodes? I refuse to merge!"). Of course, the extremely cool thing about Irmin's bidirectional mappings is that existing hosts can still bridge into the Irmin communication system just by sending a normal protocol packet! So Luke's hard work on mDNS isn't obsolete for a few decades yet :-) -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 Apr 12 06:14:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 06:14:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhBAM-0003IG-KM; Sun, 12 Apr 2015 06:14:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhBAM-0003IB-3g for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 06:14:46 +0000 Received: from [85.158.139.211] by server-8.bemta-5.messagelabs.com id 10/8A-19484-55D0A255; Sun, 12 Apr 2015 06:14:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-206.messagelabs.com!1428819284!15245579!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3202 invoked from network); 12 Apr 2015 06:14:44 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2015 06:14:44 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 966eafd5; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 12 Apr 2015 07:14:43 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5526F1A8.7040203@somerandomidiot.com> Date: Sun, 12 Apr 2015 14:14:36 +0800 Message-Id: <8CB2BF41-F54D-461E-9958-EF8F6440144F@recoil.org> References: <5526B66C.2000601@somerandomidiot.com> <5526F1A8.7040203@somerandomidiot.com> To: Mindy Preston X-Mailer: Apple Mail (2.2098) Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] irmin + mirage-vnetif + alcotest + good ol' arp 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 Apr 2015, at 05:39, Mindy wrote: > > On 04/09/2015 07:30 PM, Thomas Gazagnaire wrote: >>> I'm not that far into doing anything interesting with this pile of code, but I wanted to solicit your thoughts and feedback given all the mumbling and general noise-making about testing we've been doing. >>> >>> Thanks for your consideration and support. :) >> That's awesome! >> >> I haven't checked the code yet, but is the mapping bi-directionnal, i.e. can you modify the ARP table in the Git repository, commit and then it's picked up by the ARP code? > Yes, it should work this way (once there's more code in place). <...> >> Not related to testing, but that would be cool to find a clever use for git pull/push between unikernels (replacing ARP broadcast maybe?) > I'd been thinking about (or maybe remembered talking about with someone else?) pre-seeding newly booted unikernels with caches reflecting the current state of the local network, which is a less general case of what you propose. That was me -- the idea is tied into the above two points I've quoted. Once you establish Irmin as a trusted communications channel between two unikernels, then you can start using it to feed in state as well. ARP broadcast is obviously a very legacy way to discover other hosts on the network, and so is one of the first places where we could start providing a migration path away from rather high-latency mechanisms such as multicast DNS and broadcast protocols, towards something that can very efficiently communicate a change of states to all other nodes. In addition to being more efficient, it's also easier to build a stronger trust model ("where did this ARP update come from? Why is it different from all the other nodes? I refuse to merge!"). Of course, the extremely cool thing about Irmin's bidirectional mappings is that existing hosts can still bridge into the Irmin communication system just by sending a normal protocol packet! So Luke's hard work on mDNS isn't obsolete for a few decades yet :-) -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 Apr 12 08:48:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 08:48: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 1YhDZ0-0004bM-Fm; Sun, 12 Apr 2015 08:48:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhDYz-0004bH-RD for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 08:48:21 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id A5/3A-04861-4513A255; Sun, 12 Apr 2015 08:48:20 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1428828499!15713070!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22881 invoked from network); 12 Apr 2015 08:48:19 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 12 Apr 2015 08:48:19 -0000 Received: by lagv1 with SMTP id v1so38404178lag.3 for ; Sun, 12 Apr 2015 01:48:19 -0700 (PDT) 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=EdXd09EOKcgSwP2D/0yim+/QJqv6xa7EKdksNA2lWL8=; b=iL7WPirQB3UXBq9oVnwtZHOT2sDLhgghno9SS1JFuahcLysx+raBfWFRH5dYvtzuh5 Quy1ebpF3OHKQZsrZLJkt6FC372bERnUgTWo4fsnbO4m9udtLgnCQnJvUWUHbqoqCmlJ NLZBVYMyNUfISGmiybgsdpki6ZOVxuRjO/KR3hFL0s6ok0FZzN6iZayemUNspZhZWQSa diHY9dnL5NNRIOWgbO3DKgCL0PxLT0rw3tTU7tgsC+vP6nTQE2/h4B7ZIXKHhy7jICkE +4oHboTrq2UXofTK4b9FJ3p6SdDcV3f6G9GrbRTrT4fukuiyn4U6thWGThzzO5nMsct6 01OA== MIME-Version: 1.0 X-Received: by 10.112.89.71 with SMTP id bm7mr8507299lbb.20.1428828499139; Sun, 12 Apr 2015 01:48:19 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sun, 12 Apr 2015 01:48:19 -0700 (PDT) In-Reply-To: References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> Date: Sun, 12 Apr 2015 09:48:19 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 April 2015 at 19:18, Thomas Gazagnaire wrote: >> There are two cases. If the branch already contains a commit: >> 1. I use View.of_path to get the view. >> 2. I use BC.of_head to make a temporary branch. >> 3. I commit to the temporary branch with View.update_path. >> 4. After testing the commit, I use BC.compare_and_set_head to commit >> to the main branch. >> >> If the branch is empty: >> 1. I use View.empty to get the view. >> 2. I commit directly to the master branch with View.update_path (no >> testing is possible in this case). >> >> This works - it would just be a bit neater if there was a uniform way >> to make a commit from a view. > > Agreed. I have a ticket open to be able to start an empty store with a named branch. I should fix it and that should help. >> >>> I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: >>> 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; >>> 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. >>> 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. >>> >>> I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? >> >> Sounds good to me. Thanks! > > I've done that in https://github.com/mirage/irmin/pull/188 That's great :-) I've updated my code to use this and I've started writing my own merge logic. I had some trouble checking it with git due to https://github.com/mirage/irmin/issues/190 but it's not a major problem. Thanks! -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 12 08:48:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 08:48: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 1YhDZ0-0004bM-Fm; Sun, 12 Apr 2015 08:48:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhDYz-0004bH-RD for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 08:48:21 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id A5/3A-04861-4513A255; Sun, 12 Apr 2015 08:48:20 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1428828499!15713070!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22881 invoked from network); 12 Apr 2015 08:48:19 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 12 Apr 2015 08:48:19 -0000 Received: by lagv1 with SMTP id v1so38404178lag.3 for ; Sun, 12 Apr 2015 01:48:19 -0700 (PDT) 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=EdXd09EOKcgSwP2D/0yim+/QJqv6xa7EKdksNA2lWL8=; b=iL7WPirQB3UXBq9oVnwtZHOT2sDLhgghno9SS1JFuahcLysx+raBfWFRH5dYvtzuh5 Quy1ebpF3OHKQZsrZLJkt6FC372bERnUgTWo4fsnbO4m9udtLgnCQnJvUWUHbqoqCmlJ NLZBVYMyNUfISGmiybgsdpki6ZOVxuRjO/KR3hFL0s6ok0FZzN6iZayemUNspZhZWQSa diHY9dnL5NNRIOWgbO3DKgCL0PxLT0rw3tTU7tgsC+vP6nTQE2/h4B7ZIXKHhy7jICkE +4oHboTrq2UXofTK4b9FJ3p6SdDcV3f6G9GrbRTrT4fukuiyn4U6thWGThzzO5nMsct6 01OA== MIME-Version: 1.0 X-Received: by 10.112.89.71 with SMTP id bm7mr8507299lbb.20.1428828499139; Sun, 12 Apr 2015 01:48:19 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sun, 12 Apr 2015 01:48:19 -0700 (PDT) In-Reply-To: References: <53DA75E3-EE46-4107-8CDC-EEBFE5D51F45@gazagnaire.org> <400A4287-9E91-4587-990C-2E00335162CF@gazagnaire.org> <7773C0DA-D9A4-46D9-91C4-8AE941260009@gazagnaire.org> <26D7EFE4-4AF5-478D-A437-E6990DD1DAB8@gazagnaire.org> Date: Sun, 12 Apr 2015 09:48:19 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging in Irmin 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 April 2015 at 19:18, Thomas Gazagnaire wrote: >> There are two cases. If the branch already contains a commit: >> 1. I use View.of_path to get the view. >> 2. I use BC.of_head to make a temporary branch. >> 3. I commit to the temporary branch with View.update_path. >> 4. After testing the commit, I use BC.compare_and_set_head to commit >> to the main branch. >> >> If the branch is empty: >> 1. I use View.empty to get the view. >> 2. I commit directly to the master branch with View.update_path (no >> testing is possible in this case). >> >> This works - it would just be a bit neater if there was a uniform way >> to make a commit from a view. > > Agreed. I have a ticket open to be able to start an empty store with a named branch. I should fix it and that should help. >> >>> I've been playing with that API a little bit but that's not very easy to do actually (currently View depends on BC, and adding your function will make the whole thing recursive). I can either: >>> 1. add the function in View (ie. `View.make_head: db -> task -> parents:head list -> contents:t -> head`) which is a bit weird but should work; >>> 2/ or I can expose a staging area as a HRW store (i.e. without the subpath functions which appear in the View signature), so all updates should go through that module and that will be incompatible with normal views. >>> 3. or I can implement immutable views to have a proper staging area using immutable prefix trees. >>> >>> I'm in favour of 1. for now on and hopefully one day we'll have 3. Is it fine with you? >> >> Sounds good to me. Thanks! > > I've done that in https://github.com/mirage/irmin/pull/188 That's great :-) I've updated my code to use this and I've started writing my own merge logic. I had some trouble checking it with git due to https://github.com/mirage/irmin/issues/190 but it's not a major problem. Thanks! -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 12 08:51:22 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 08:51: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 1YhDbt-0005By-QI; Sun, 12 Apr 2015 08:51:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhDbs-0005Bt-QP for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 08:51:21 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id D7/68-07318-8023A255; Sun, 12 Apr 2015 08:51:20 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1428828679!15553700!1 X-Originating-IP: [209.85.217.175] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 381 invoked from network); 12 Apr 2015 08:51:19 -0000 Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 12 Apr 2015 08:51:19 -0000 Received: by lbbqq2 with SMTP id qq2so39458926lbb.3 for ; Sun, 12 Apr 2015 01:51:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=IocutzgQ1a5ugmU48Fpql/QKLq29o0c2b/+2VbI1i/Q=; b=JokV4ab4g1W8fAkG75EY5zhzlbZoe8TunrHrnVycl14voupwn75SX4RZlDqgr7x9+c 7o1++Dy3ErYnRs/Npo//EHt0Pvbm4gOyCaDsn0tGHgOOwv59qLk6krtKVZQ+xrmCDriS /HWwrYALgtGEXPHnyphuYrB2zyYETkx3jIvzr88NT/cVvg900rZ3CRmtCx3WFjpacmbP 0dC3wxyBANm3sZQEXb3bO77++nHU//gSlhOvpORNox5qmG85bbm6gGkukhQShY1pMQCA 4a6vfUD2p5aVAq4JuCLkrG75Oh0sGBoW4t4234lg5BtumTIqF97o3l9CX6sQi0s/qQPk JKJQ== X-Gm-Message-State: ALoCoQmLz0JmkeLM/fGGdX7jjgAIx0CuC4g1eVLA1X81PiuYq0T1rB2b0S0ivd3Oz/70z3AoJISH X-Received: by 10.112.150.130 with SMTP id ui2mr8378012lbb.116.1428828678603; Sun, 12 Apr 2015 01:51:18 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id kx8sm906259lbc.3.2015.04.12.01.51.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Apr 2015 01:51:17 -0700 (PDT) Date: Sun, 12 Apr 2015 10:51:14 +0200 From: Magnus Therning To: Anil Madhavapeddy Message-ID: <20150412085114.GA2554@tatooine> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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="===============8165869570158915701==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8165869570158915701== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 11, 2015 at 11:33:40PM +0800, Anil Madhavapeddy wrote: > On 11 Apr 2015, at 23:13, Magnus Skjegstad wrote: > >=20 > > On Fri, 10 Apr 2015, at 05:29, Magnus Therning wrote: > >> On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: > >> [...] > >> I did a little bit more testing of this just now, and found something > >> surprising. This is against a VM on ARM: > >>=20 > >> ~~~ > >> % echo thisisalongerstring | ncat -4 192.168.0.33 18080 > >> alongerstring > >>=20 > >> -> > >>=20 > >> tcp: 192.168.0.11:48731 > >> 6 -=20 > >> 14 - alongerstring > >> ~~~ > >>=20 > >> and > >>=20 > >> ~~~ > >> % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 > >> 18080 > >> alongerstringandthisislongerstill > >>=20 > >> -> > >>=20 > >> tcp: 192.168.0.11:48732 > >> 6 -=20 > >> 34 - alongerstringandthisislongerstill > >> ~~~ > >>=20 > >> and if I send a string that is shorter than 6 characters (I'm guessing > >> including the trailing \r\n), then `ncat` hangs and on the ARM I only > >> see a single line of "length - content": > >>=20 > >> ~~~ > >> tcp: 192.168.0.11:48766 > >> 6 - > >> ~~~ > >>=20 > >> I do wonder where those initial 6 characters go... > >>=20 > >=20 > > Hm - I am able to reproduce this. I have a cubieboard and an x86 Xen > > server connected to the same switch. If I run the unikernel above on the > > x86 server I can access it remotely and from dom0 without problems. It > > also works fine if I run the unikernel in Xen on the cubieboard and try > > to access it from dom0: > >=20 > >=20 > > I am using tcpip 2.3.1 and mirage-net-xen 1.4.1.=20 >=20 > Can you bisect backwards a few versions to check if this goes away? > I'm a few thousands miles away from my Cubies until Tuesday, so can't > try this out myself. The usual culprit for such problems is TCP > offload, but this sounds like more of a physical driver issue. As > another datapoint, does a Linux domU VM have networking? I backed to tcpip 2.3.0 (before the assert "fix") then 1. `ncat` from dom0 works just fine, no assert and full string received and returned. 2. `ncat` from my PC triggers the assert, the full string is received and returned, but `ncat` hangs. Is there some pre-packaged ARM Linux guest image to download from somewhere? /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Would you go to war without a helmet? Would you drive without the seat belt? Then why do you develop software as if shit doesn=E2=80=99t happen? -- Alberto G ( http://makinggoodsoftware.com/2009/05/12/hdd/ ) --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUqMfYACgkQiMWTaatN+6SjlACeMfdALc0iXlV38ZqdKvTaF/vb qrsAoJjTGbV8tFexDVXwY8/3OQNjmzbv =DEY6 -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- --===============8165869570158915701== 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 --===============8165869570158915701==-- From mirageos-devel-bounces@lists.xenproject.org Sun Apr 12 08:51:22 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 08:51: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 1YhDbt-0005By-QI; Sun, 12 Apr 2015 08:51:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhDbs-0005Bt-QP for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 08:51:21 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id D7/68-07318-8023A255; Sun, 12 Apr 2015 08:51:20 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1428828679!15553700!1 X-Originating-IP: [209.85.217.175] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 381 invoked from network); 12 Apr 2015 08:51:19 -0000 Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 12 Apr 2015 08:51:19 -0000 Received: by lbbqq2 with SMTP id qq2so39458926lbb.3 for ; Sun, 12 Apr 2015 01:51:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=IocutzgQ1a5ugmU48Fpql/QKLq29o0c2b/+2VbI1i/Q=; b=JokV4ab4g1W8fAkG75EY5zhzlbZoe8TunrHrnVycl14voupwn75SX4RZlDqgr7x9+c 7o1++Dy3ErYnRs/Npo//EHt0Pvbm4gOyCaDsn0tGHgOOwv59qLk6krtKVZQ+xrmCDriS /HWwrYALgtGEXPHnyphuYrB2zyYETkx3jIvzr88NT/cVvg900rZ3CRmtCx3WFjpacmbP 0dC3wxyBANm3sZQEXb3bO77++nHU//gSlhOvpORNox5qmG85bbm6gGkukhQShY1pMQCA 4a6vfUD2p5aVAq4JuCLkrG75Oh0sGBoW4t4234lg5BtumTIqF97o3l9CX6sQi0s/qQPk JKJQ== X-Gm-Message-State: ALoCoQmLz0JmkeLM/fGGdX7jjgAIx0CuC4g1eVLA1X81PiuYq0T1rB2b0S0ivd3Oz/70z3AoJISH X-Received: by 10.112.150.130 with SMTP id ui2mr8378012lbb.116.1428828678603; Sun, 12 Apr 2015 01:51:18 -0700 (PDT) Received: from tatooine (c83-248-178-110.bredband.comhem.se. [83.248.178.110]) by mx.google.com with ESMTPSA id kx8sm906259lbc.3.2015.04.12.01.51.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Apr 2015 01:51:17 -0700 (PDT) Date: Sun, 12 Apr 2015 10:51:14 +0200 From: Magnus Therning To: Anil Madhavapeddy Message-ID: <20150412085114.GA2554@tatooine> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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="===============8165869570158915701==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8165869570158915701== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 11, 2015 at 11:33:40PM +0800, Anil Madhavapeddy wrote: > On 11 Apr 2015, at 23:13, Magnus Skjegstad wrote: > >=20 > > On Fri, 10 Apr 2015, at 05:29, Magnus Therning wrote: > >> On Thu, Apr 09, 2015 at 10:18:53PM +0200, Magnus Therning wrote: > >> [...] > >> I did a little bit more testing of this just now, and found something > >> surprising. This is against a VM on ARM: > >>=20 > >> ~~~ > >> % echo thisisalongerstring | ncat -4 192.168.0.33 18080 > >> alongerstring > >>=20 > >> -> > >>=20 > >> tcp: 192.168.0.11:48731 > >> 6 -=20 > >> 14 - alongerstring > >> ~~~ > >>=20 > >> and > >>=20 > >> ~~~ > >> % echo thisisalongerstringandthisislongerstill | ncat -4 192.168.0.33 > >> 18080 > >> alongerstringandthisislongerstill > >>=20 > >> -> > >>=20 > >> tcp: 192.168.0.11:48732 > >> 6 -=20 > >> 34 - alongerstringandthisislongerstill > >> ~~~ > >>=20 > >> and if I send a string that is shorter than 6 characters (I'm guessing > >> including the trailing \r\n), then `ncat` hangs and on the ARM I only > >> see a single line of "length - content": > >>=20 > >> ~~~ > >> tcp: 192.168.0.11:48766 > >> 6 - > >> ~~~ > >>=20 > >> I do wonder where those initial 6 characters go... > >>=20 > >=20 > > Hm - I am able to reproduce this. I have a cubieboard and an x86 Xen > > server connected to the same switch. If I run the unikernel above on the > > x86 server I can access it remotely and from dom0 without problems. It > > also works fine if I run the unikernel in Xen on the cubieboard and try > > to access it from dom0: > >=20 > >=20 > > I am using tcpip 2.3.1 and mirage-net-xen 1.4.1.=20 >=20 > Can you bisect backwards a few versions to check if this goes away? > I'm a few thousands miles away from my Cubies until Tuesday, so can't > try this out myself. The usual culprit for such problems is TCP > offload, but this sounds like more of a physical driver issue. As > another datapoint, does a Linux domU VM have networking? I backed to tcpip 2.3.0 (before the assert "fix") then 1. `ncat` from dom0 works just fine, no assert and full string received and returned. 2. `ncat` from my PC triggers the assert, the full string is received and returned, but `ncat` hangs. Is there some pre-packaged ARM Linux guest image to download from somewhere? /M --=20 Magnus Therning OpenPGP: 0xAB4DFBA4=20 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Would you go to war without a helmet? Would you drive without the seat belt? Then why do you develop software as if shit doesn=E2=80=99t happen? -- Alberto G ( http://makinggoodsoftware.com/2009/05/12/hdd/ ) --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlUqMfYACgkQiMWTaatN+6SjlACeMfdALc0iXlV38ZqdKvTaF/vb qrsAoJjTGbV8tFexDVXwY8/3OQNjmzbv =DEY6 -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- --===============8165869570158915701== 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 --===============8165869570158915701==-- From mirageos-devel-bounces@lists.xenproject.org Sun Apr 12 09:01:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 09:01: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 1YhDlj-0005qN-Uq; Sun, 12 Apr 2015 09:01:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhDli-0005qI-EP for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 09:01:30 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 98/B1-23180-9643A255; Sun, 12 Apr 2015 09:01:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1428829288!12586560!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19298 invoked from network); 12 Apr 2015 09:01:28 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2015 09:01:28 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 257dfd68; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 12 Apr 2015 10:01:27 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <20150412085114.GA2554@tatooine> Date: Sun, 12 Apr 2015 17:01:18 +0800 Message-Id: <183B92E9-952B-4C69-92F9-F05E0597E179@recoil.org> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> <20150412085114.GA2554@tatooine> To: Magnus Therning X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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 Apr 2015, at 16:51, Magnus Therning wrote: > > On Sat, Apr 11, 2015 at 11:33:40PM +0800, Anil Madhavapeddy wrote: >> On 11 Apr 2015, at 23:13, Magnus Skjegstad wrote: >>> > I backed to tcpip 2.3.0 (before the assert "fix") then > > 1. `ncat` from dom0 works just fine, no assert and full string > received and returned. > 2. `ncat` from my PC triggers the assert, the full string is received > and returned, but `ncat` hangs. The perfect bisection, thank you! This means that the Cstruct length is shorter than the advertised packet length in the IP header for some reason. See: https://github.com/mirage/mirage-tcpip/pull/122/files#diff-1b30afa1d7f89fe0693b36ef4006c6f4L178 Some more debugging around what the various values are would pin down the problem. You could put in some Printf.printfs around the TCPIP code and see what comes out on the VM console. > > Is there some pre-packaged ARM Linux guest image to download from > somewhere? There's a create-linux-guest script in /root of the Cubie/Xen image. That should debootstrap you up a guest quite conveniently. However, it looks like you've pinpointed the problem source in the TCPIP code (that only triggers on ARM). -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 Apr 12 09:01:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 12 Apr 2015 09:01: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 1YhDlj-0005qN-Uq; Sun, 12 Apr 2015 09:01:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhDli-0005qI-EP for mirageos-devel@lists.xenproject.org; Sun, 12 Apr 2015 09:01:30 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 98/B1-23180-9643A255; Sun, 12 Apr 2015 09:01:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1428829288!12586560!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19298 invoked from network); 12 Apr 2015 09:01:28 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2015 09:01:28 -0000 Received: from [192.168.2.106] (nusnet-195-10.dynip.nus.edu.sg [137.132.195.10]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 257dfd68; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 12 Apr 2015 10:01:27 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <20150412085114.GA2554@tatooine> Date: Sun, 12 Apr 2015 17:01:18 +0800 Message-Id: <183B92E9-952B-4C69-92F9-F05E0597E179@recoil.org> References: <20150409201853.GA11002@tatooine> <20150410042935.GA27321@tatooine> <1428765230.2042101.252086709.37214F79@webmail.messagingengine.com> <20150412085114.GA2554@tatooine> To: Magnus Therning X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] More troubles with tcp on ARM 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 Apr 2015, at 16:51, Magnus Therning wrote: > > On Sat, Apr 11, 2015 at 11:33:40PM +0800, Anil Madhavapeddy wrote: >> On 11 Apr 2015, at 23:13, Magnus Skjegstad wrote: >>> > I backed to tcpip 2.3.0 (before the assert "fix") then > > 1. `ncat` from dom0 works just fine, no assert and full string > received and returned. > 2. `ncat` from my PC triggers the assert, the full string is received > and returned, but `ncat` hangs. The perfect bisection, thank you! This means that the Cstruct length is shorter than the advertised packet length in the IP header for some reason. See: https://github.com/mirage/mirage-tcpip/pull/122/files#diff-1b30afa1d7f89fe0693b36ef4006c6f4L178 Some more debugging around what the various values are would pin down the problem. You could put in some Printf.printfs around the TCPIP code and see what comes out on the VM console. > > Is there some pre-packaged ARM Linux guest image to download from > somewhere? There's a create-linux-guest script in /root of the Cubie/Xen image. That should debootstrap you up a guest quite conveniently. However, it looks like you've pinpointed the problem source in the TCPIP code (that only triggers on ARM). -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 Apr 13 02:55:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Apr 2015 02:55: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 1YhUWd-0001It-RT; Mon, 13 Apr 2015 02:55:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhUWc-0001Io-KW for mirageos-devel@lists.xenproject.org; Mon, 13 Apr 2015 02:55:02 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id 7C/2E-14044-5003B255; Mon, 13 Apr 2015 02:55:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1428893700!11213314!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.0 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MIME_QP_LONG_LINE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16292 invoked from network); 13 Apr 2015 02:55:00 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Apr 2015 02:55:00 -0000 Received: from [192.168.224.195] (84-37.comp.nus.edu.sg [137.132.84.37]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 44fc70e9; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 13 Apr 2015 03:54:59 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5F30557E-1C79-4F20-86AA-6BD25D692F2E@gazagnaire.org> Date: Mon, 13 Apr 2015 10:54:54 +0800 Message-Id: References: <5F30557E-1C79-4F20-86AA-6BD25D692F2E@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] What was the reasoning for splitting out mirage-http? 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="===============8772009572400809891==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8772009572400809891== Content-Type: multipart/alternative; boundary="Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0" --Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 9 Apr 2015, at 00:52, Thomas Gazagnaire = wrote: >=20 >> Back in 2013, mirage-http was extracted out of cohttp into it=E2=80=99s= own repository. Although I=E2=80=99m ignorant of how the decision was = made, I understand that there could have been good reasons for this a = couple of years ago. Today, however, it seems like there=E2=80=99s less = good reasons for such a split. Now that opam supports multiple packages = out of the same repo and since we=E2=80=99re planning on releasing = cohttp backends as their own packages [1], maybe it makes sense to treat = mirage-http the same way? >=20 > Yes, we wanted to have a separate opam package for mirage-http, and at = the time it was the only possible option (now, with .opam, it = would be possible to keep the code in the same repository). >=20 > However I think having the code outside in this case is better (even = though not necessary easier) as we also need to synchronise the release = of mirage-http with the mirage tool (which generates some code using = mirage-http). So I think, having a separate release schedule for cohttp = and mirage-cohttp (and thus separate repositories and maintainers) makes = sense in that case even if it can cause some trouble to the maintainers. I agree with this. It does however highlight the need for a = reverse-dependency checking tool to figure out whether or not a pull = request dramatically breaks something or not. I'll work on this with = David Sheets (who has done much of the GitHub work necessary), and it's = a good excuse to use Irmin as well. -anil= --Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On 9 Apr 2015, at 00:52, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:

Back in 2013, mirage-http was extracted out of cohttp into = it=E2=80=99s own repository. Although I=E2=80=99m ignorant of how the = decision was made, I understand that there could have been good reasons = for this a couple of years ago. Today, however, it seems like there=E2=80=99= s less good reasons for such a split. Now that opam supports multiple = packages out of the same repo and since we=E2=80=99re planning on = releasing cohttp backends as their own packages [1], maybe it makes = sense to treat mirage-http the same = way?

Yes, we wanted to have a separate opam = package for mirage-http, and at the time it was the only possible option = (now, with <package>.opam, it would be possible to keep the code = in the same repository).

However I think having the code outside in this case is = better (even though not necessary easier) as we also need to synchronise = the release of mirage-http with the mirage tool (which generates some = code using mirage-http). So I think, having a separate release schedule = for cohttp and mirage-cohttp (and thus separate repositories and = maintainers) makes sense in that case even if it can cause some trouble = to the maintainers.

I agree with this.  It does however highlight the = need for a reverse-dependency checking tool to figure out whether or not = a pull request dramatically breaks something or not.  I'll work on = this with David Sheets (who has done much of the GitHub work necessary), = and it's a good excuse to use Irmin as well.

-anil
= --Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0-- --===============8772009572400809891== 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 --===============8772009572400809891==-- From mirageos-devel-bounces@lists.xenproject.org Mon Apr 13 02:55:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Apr 2015 02:55: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 1YhUWd-0001It-RT; Mon, 13 Apr 2015 02:55:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhUWc-0001Io-KW for mirageos-devel@lists.xenproject.org; Mon, 13 Apr 2015 02:55:02 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id 7C/2E-14044-5003B255; Mon, 13 Apr 2015 02:55:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1428893700!11213314!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.0 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MIME_QP_LONG_LINE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16292 invoked from network); 13 Apr 2015 02:55:00 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Apr 2015 02:55:00 -0000 Received: from [192.168.224.195] (84-37.comp.nus.edu.sg [137.132.84.37]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 44fc70e9; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 13 Apr 2015 03:54:59 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5F30557E-1C79-4F20-86AA-6BD25D692F2E@gazagnaire.org> Date: Mon, 13 Apr 2015 10:54:54 +0800 Message-Id: References: <5F30557E-1C79-4F20-86AA-6BD25D692F2E@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] What was the reasoning for splitting out mirage-http? 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="===============8772009572400809891==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8772009572400809891== Content-Type: multipart/alternative; boundary="Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0" --Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 9 Apr 2015, at 00:52, Thomas Gazagnaire = wrote: >=20 >> Back in 2013, mirage-http was extracted out of cohttp into it=E2=80=99s= own repository. Although I=E2=80=99m ignorant of how the decision was = made, I understand that there could have been good reasons for this a = couple of years ago. Today, however, it seems like there=E2=80=99s less = good reasons for such a split. Now that opam supports multiple packages = out of the same repo and since we=E2=80=99re planning on releasing = cohttp backends as their own packages [1], maybe it makes sense to treat = mirage-http the same way? >=20 > Yes, we wanted to have a separate opam package for mirage-http, and at = the time it was the only possible option (now, with .opam, it = would be possible to keep the code in the same repository). >=20 > However I think having the code outside in this case is better (even = though not necessary easier) as we also need to synchronise the release = of mirage-http with the mirage tool (which generates some code using = mirage-http). So I think, having a separate release schedule for cohttp = and mirage-cohttp (and thus separate repositories and maintainers) makes = sense in that case even if it can cause some trouble to the maintainers. I agree with this. It does however highlight the need for a = reverse-dependency checking tool to figure out whether or not a pull = request dramatically breaks something or not. I'll work on this with = David Sheets (who has done much of the GitHub work necessary), and it's = a good excuse to use Irmin as well. -anil= --Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On 9 Apr 2015, at 00:52, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:

Back in 2013, mirage-http was extracted out of cohttp into = it=E2=80=99s own repository. Although I=E2=80=99m ignorant of how the = decision was made, I understand that there could have been good reasons = for this a couple of years ago. Today, however, it seems like there=E2=80=99= s less good reasons for such a split. Now that opam supports multiple = packages out of the same repo and since we=E2=80=99re planning on = releasing cohttp backends as their own packages [1], maybe it makes = sense to treat mirage-http the same = way?

Yes, we wanted to have a separate opam = package for mirage-http, and at the time it was the only possible option = (now, with <package>.opam, it would be possible to keep the code = in the same repository).

However I think having the code outside in this case is = better (even though not necessary easier) as we also need to synchronise = the release of mirage-http with the mirage tool (which generates some = code using mirage-http). So I think, having a separate release schedule = for cohttp and mirage-cohttp (and thus separate repositories and = maintainers) makes sense in that case even if it can cause some trouble = to the maintainers.

I agree with this.  It does however highlight the = need for a reverse-dependency checking tool to figure out whether or not = a pull request dramatically breaks something or not.  I'll work on = this with David Sheets (who has done much of the GitHub work necessary), = and it's a good excuse to use Irmin as well.

-anil
= --Apple-Mail=_FF7293AA-2BD0-47BC-9783-CC2970E23FB0-- --===============8772009572400809891== 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 --===============8772009572400809891==-- From mirageos-devel-bounces@lists.xenproject.org Mon Apr 13 16:34:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Apr 2015 16:34:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhhJQ-0008KN-Nt; Mon, 13 Apr 2015 16:34:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhhJP-0008KI-M9 for mirageos-devel@lists.xenproject.org; Mon, 13 Apr 2015 16:34:15 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id 82/B2-32487-600FB255; Mon, 13 Apr 2015 16:34:14 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1428942851!16029987!1 X-Originating-IP: [209.85.217.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12410 invoked from network); 13 Apr 2015 16:34:11 -0000 Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Apr 2015 16:34:11 -0000 Received: by lbbuc2 with SMTP id uc2so63750329lbb.2 for ; Mon, 13 Apr 2015 09:34:11 -0700 (PDT) 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=BO64rsfAtwX9PM4uajdg/9Xz1t1fd/oiehgjVcQIm4E=; b=J+u9294Pz4aJ/9eFQYoWxWgmtn9zqZKuazjTWm5S32u9XUqQaM1fnDieYwmObh8YVx KUeHvk/eoPddpnvPP5O0YM6gezDwLTkhTlX6AUPsBwDv4gH7pGlfbytOfXmVKI8w6CMD HPEB47DX9O8d4c+CyWCaJG19lYZAdMcq37qgb4oAGo9dnGSMqR9zgqFIdsGKDOJX5Hbb tzXiWJu8zZ+kDMp91ALfpYF83drAz8GABXNQqry1Fup5zGJBMVGlyg9urSZL6DEO/2UO 2dnVXpSmAqd1y5j83di2aIcCUOQFznd93x+Mmt1OWCN1IKplJNgCnQCFw+OkdR8IcL/7 5aiA== MIME-Version: 1.0 X-Received: by 10.152.26.130 with SMTP id l2mr14161322lag.20.1428942851156; Mon, 13 Apr 2015 09:34:11 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Mon, 13 Apr 2015 09:34:11 -0700 (PDT) In-Reply-To: References: Date: Mon, 13 Apr 2015 17:34:11 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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 April 2015 at 05:33, Anil Madhavapeddy wrote: > On 11 Apr 2015, at 00:28, Thomas Leonard wrote: >> >> On 10 April 2015 at 12:26, Nick Betteridge wrote: >>> I've just received a Cubieboard4 and I'm trying to work out what's needed to >>> add it to blobs.openmirage.org. >>> >>> Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd, there are two >>> sections which differ: >>> >>> 1. The address locations: kernel, ramdisk etc. >>> 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. >>> >>> Does anyone have any idea on where to derive the (1)? >> >> I got the original information from here: >> >> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner >> >> I think the CB4 has the same amount of memory as the CB3, so it might >> be fine as-is. >> >>> The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dts >>> & sun9i-a80.dtsi). >>> >>> Also, is there anything else I've missed and need to take care of? >> > > I've ordered one for myself as well. The extra RAM will certainly > come in useful for deployments! > > If you have a setup with a serial cable, something else to experiment > with is to upgrade the version of Xen that's supplied to Xen 4.5. > The current Xen 4.4-rc had a limitation that half of the board memory > can't be assigned to domUs, and I think that got fixed in Xen 4.5. > Thomas, do you remember the details of this? As far as I know that's the case for Dom0: http://wiki.xen.org/wiki/Xen_ARM_TODO#Domain_0_memory_limitation_due_to_1:1_mapping It doesn't mention any limit for DomUs, but that wouldn't normally affect unikernels. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 13 16:34:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Apr 2015 16:34:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhhJQ-0008KN-Nt; Mon, 13 Apr 2015 16:34:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YhhJP-0008KI-M9 for mirageos-devel@lists.xenproject.org; Mon, 13 Apr 2015 16:34:15 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id 82/B2-32487-600FB255; Mon, 13 Apr 2015 16:34:14 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1428942851!16029987!1 X-Originating-IP: [209.85.217.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12410 invoked from network); 13 Apr 2015 16:34:11 -0000 Received: from mail-lb0-f169.google.com (HELO mail-lb0-f169.google.com) (209.85.217.169) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Apr 2015 16:34:11 -0000 Received: by lbbuc2 with SMTP id uc2so63750329lbb.2 for ; Mon, 13 Apr 2015 09:34:11 -0700 (PDT) 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=BO64rsfAtwX9PM4uajdg/9Xz1t1fd/oiehgjVcQIm4E=; b=J+u9294Pz4aJ/9eFQYoWxWgmtn9zqZKuazjTWm5S32u9XUqQaM1fnDieYwmObh8YVx KUeHvk/eoPddpnvPP5O0YM6gezDwLTkhTlX6AUPsBwDv4gH7pGlfbytOfXmVKI8w6CMD HPEB47DX9O8d4c+CyWCaJG19lYZAdMcq37qgb4oAGo9dnGSMqR9zgqFIdsGKDOJX5Hbb tzXiWJu8zZ+kDMp91ALfpYF83drAz8GABXNQqry1Fup5zGJBMVGlyg9urSZL6DEO/2UO 2dnVXpSmAqd1y5j83di2aIcCUOQFznd93x+Mmt1OWCN1IKplJNgCnQCFw+OkdR8IcL/7 5aiA== MIME-Version: 1.0 X-Received: by 10.152.26.130 with SMTP id l2mr14161322lag.20.1428942851156; Mon, 13 Apr 2015 09:34:11 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Mon, 13 Apr 2015 09:34:11 -0700 (PDT) In-Reply-To: References: Date: Mon, 13 Apr 2015 17:34:11 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Cubieboard4 & xen-arm-builder 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 April 2015 at 05:33, Anil Madhavapeddy wrote: > On 11 Apr 2015, at 00:28, Thomas Leonard wrote: >> >> On 10 April 2015 at 12:26, Nick Betteridge wrote: >>> I've just received a Cubieboard4 and I'm trying to work out what's needed to >>> add it to blobs.openmirage.org. >>> >>> Comparing boot-cubieboard2.cmd and boot-cubietruck.cmd, there are two >>> sections which differ: >>> >>> 1. The address locations: kernel, ramdisk etc. >>> 2. The sun7i-a20-cubieboard2/cubietruck.dtb files. >>> >>> Does anyone have any idea on where to derive the (1)? >> >> I got the original information from here: >> >> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner >> >> I think the CB4 has the same amount of memory as the CB3, so it might >> be fine as-is. >> >>> The dtb file I can create from the linaro 15.X branch (sun9i-a80-optimus.dts >>> & sun9i-a80.dtsi). >>> >>> Also, is there anything else I've missed and need to take care of? >> > > I've ordered one for myself as well. The extra RAM will certainly > come in useful for deployments! > > If you have a setup with a serial cable, something else to experiment > with is to upgrade the version of Xen that's supplied to Xen 4.5. > The current Xen 4.4-rc had a limitation that half of the board memory > can't be assigned to domUs, and I think that got fixed in Xen 4.5. > Thomas, do you remember the details of this? As far as I know that's the case for Dom0: http://wiki.xen.org/wiki/Xen_ARM_TODO#Domain_0_memory_limitation_due_to_1:1_mapping It doesn't mention any limit for DomUs, but that wouldn't normally affect unikernels. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 14 14:14:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Apr 2015 14:14: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 1Yi1bh-0005QO-Vx; Tue, 14 Apr 2015 14:14:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yi1bg-0005QE-M2 for mirageos-devel@lists.xenproject.org; Tue, 14 Apr 2015 14:14:28 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id FD/0D-12069-3C02D255; Tue, 14 Apr 2015 14:14:27 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1429020867!16400271!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21690 invoked from network); 14 Apr 2015 14:14:27 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Apr 2015 14:14:27 -0000 Received: from [128.232.110.207] (c207.al.cl.cam.ac.uk [128.232.110.207]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (not verified)) by mail.mehnert.org (Postfix) with ESMTPS id 071E517A3 for ; Tue, 14 Apr 2015 16:14:25 +0200 (CEST) Message-ID: <552D20C3.5020102@mehnert.org> Date: Tue, 14 Apr 2015 15:14:27 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" OpenPGP: id=11B5464249B5BD858FFF6328BC896588DF7C28EE Subject: [MirageOS-devel] TLS tunnel 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, I wrote a small Unix application, which is very similar to the popular stunnel tool (and should be a dropin replacement for many use cases). It uses our OCaml-TLS library. TLS Tunnel listens on a given port for TLS connections, and forwards the unencrypted connection to a given destination on destination port. It can also write a logfile. It currently uses lwt (no mirage yet [waiting for merges]). If you want to try it out, get it at https://github.com/hannesm/tlstunnel or opam pin add tlstunnel https://github.com/hannesm/tlstunnel If you have any questions or find issues, please let me know via the issue tracker, hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVLSDDAAoJELyJZYjffCju2eoP/jc/RJPqZuSg4E76bo+m1gSt kPlkEiqzzqMJk9oAJIzBBKHY1ySgDxETjpikI6AdYqnB4rCZFJKOcAA2yRm1GOEW adFg3dc6k4WhjhvOU5jfZyiQzaEXxAN7xWBy8Lwx7z5/+A1ewmXzsD6lUTLrOYIM FDDIYHCayIxPPlQXQgI1o8ZFd8o6jNUkpHXFNE3sA6RFviQHbNVd5WTs1260qRsm zlI5shT+82jCUQOZZZ/HaJQTA3FJhvskrYJ365NJ5ieuK62o1jWT7eoUDSq34JSX x8yuOg0yA168qBzjjsj0zpDiWnCxuMVnF4ZGjEZKmribHSuMX+RKSWY5RTvr/3xe BQMVFijvTemXGPLFXgemZxNW3HIqyu4ZmIZTgiNNCoikJ3/9gZtGKU1CHJXDM31G onuaxDbfQeQNBqudL3DNUk9qUjXxLXSLFFqpSzEIoAZKFckVDsUwoDCvWyV5AtCK +JRt0QSf8I/pRBxyPSkOPSsB9/JJEfndjE67YZgiObKsBF4A24Gg3acP+sRyRXnp rNJxIzYWZkXg3ZUonHxzK42qEEnh5v4l8Qpp1ckboRKWyfgaamHrnqIvRQ4DF+Fz bCTZZDn7SWqVsat6kpLVbivqoalh2iCYrVG8IdcW8F6nV1pdB0JPTmDMKjv0nCQP UCqy65k6vOnAHgTx3mT0 =wG6/ -----END PGP SIGNATURE----- _______________________________________________ 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 Apr 14 14:14:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Apr 2015 14:14: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 1Yi1bh-0005QO-Vx; Tue, 14 Apr 2015 14:14:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yi1bg-0005QE-M2 for mirageos-devel@lists.xenproject.org; Tue, 14 Apr 2015 14:14:28 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id FD/0D-12069-3C02D255; Tue, 14 Apr 2015 14:14:27 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1429020867!16400271!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21690 invoked from network); 14 Apr 2015 14:14:27 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Apr 2015 14:14:27 -0000 Received: from [128.232.110.207] (c207.al.cl.cam.ac.uk [128.232.110.207]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (not verified)) by mail.mehnert.org (Postfix) with ESMTPS id 071E517A3 for ; Tue, 14 Apr 2015 16:14:25 +0200 (CEST) Message-ID: <552D20C3.5020102@mehnert.org> Date: Tue, 14 Apr 2015 15:14:27 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" OpenPGP: id=11B5464249B5BD858FFF6328BC896588DF7C28EE Subject: [MirageOS-devel] TLS tunnel 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, I wrote a small Unix application, which is very similar to the popular stunnel tool (and should be a dropin replacement for many use cases). It uses our OCaml-TLS library. TLS Tunnel listens on a given port for TLS connections, and forwards the unencrypted connection to a given destination on destination port. It can also write a logfile. It currently uses lwt (no mirage yet [waiting for merges]). If you want to try it out, get it at https://github.com/hannesm/tlstunnel or opam pin add tlstunnel https://github.com/hannesm/tlstunnel If you have any questions or find issues, please let me know via the issue tracker, hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVLSDDAAoJELyJZYjffCju2eoP/jc/RJPqZuSg4E76bo+m1gSt kPlkEiqzzqMJk9oAJIzBBKHY1ySgDxETjpikI6AdYqnB4rCZFJKOcAA2yRm1GOEW adFg3dc6k4WhjhvOU5jfZyiQzaEXxAN7xWBy8Lwx7z5/+A1ewmXzsD6lUTLrOYIM FDDIYHCayIxPPlQXQgI1o8ZFd8o6jNUkpHXFNE3sA6RFviQHbNVd5WTs1260qRsm zlI5shT+82jCUQOZZZ/HaJQTA3FJhvskrYJ365NJ5ieuK62o1jWT7eoUDSq34JSX x8yuOg0yA168qBzjjsj0zpDiWnCxuMVnF4ZGjEZKmribHSuMX+RKSWY5RTvr/3xe BQMVFijvTemXGPLFXgemZxNW3HIqyu4ZmIZTgiNNCoikJ3/9gZtGKU1CHJXDM31G onuaxDbfQeQNBqudL3DNUk9qUjXxLXSLFFqpSzEIoAZKFckVDsUwoDCvWyV5AtCK +JRt0QSf8I/pRBxyPSkOPSsB9/JJEfndjE67YZgiObKsBF4A24Gg3acP+sRyRXnp rNJxIzYWZkXg3ZUonHxzK42qEEnh5v4l8Qpp1ckboRKWyfgaamHrnqIvRQ4DF+Fz bCTZZDn7SWqVsat6kpLVbivqoalh2iCYrVG8IdcW8F6nV1pdB0JPTmDMKjv0nCQP UCqy65k6vOnAHgTx3mT0 =wG6/ -----END PGP SIGNATURE----- _______________________________________________ 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 Apr 15 12:30:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Apr 2015 12:30:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YiMSp-0000TW-CX; Wed, 15 Apr 2015 12:30:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YiMSo-0000Sp-HL for mirageos-devel@lists.xenproject.org; Wed, 15 Apr 2015 12:30:42 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id FD/C7-05046-1F95E255; Wed, 15 Apr 2015 12:30:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1429101040!18141058!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP, UPPERCASE_25_50 X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23806 invoked from network); 15 Apr 2015 12:30:40 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Apr 2015 12:30:40 -0000 Received: from [IPv6:::1] (localhost [127.0.0.1]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 63b6a4fa; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 15 Apr 2015 13:30:39 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <552D20C3.5020102@mehnert.org> Date: Wed, 15 Apr 2015 13:30:40 +0100 Message-Id: References: <552D20C3.5020102@mehnert.org> To: Hannes Mehnert , Yaron Minsky X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TLS tunnel 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 Looks great! I've created a few issues that would be useful to fix before putting this into production use. I'm going to deploy this to replace stud on https://realworldocaml.org shortly... Anil > On 14 Apr 2015, at 15:14, Hannes Mehnert wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > I wrote a small Unix application, which is very similar to the popular > stunnel tool (and should be a dropin replacement for many use cases). > It uses our OCaml-TLS library. > > TLS Tunnel listens on a given port for TLS connections, and forwards the > unencrypted connection to a given destination on destination port. It > can also write a logfile. > > It currently uses lwt (no mirage yet [waiting for merges]). If you > want to try it out, get it at https://github.com/hannesm/tlstunnel > > or opam pin add tlstunnel https://github.com/hannesm/tlstunnel > > > If you have any questions or find issues, please let me know via the > issue tracker, > > hannes > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCQAGBQJVLSDDAAoJELyJZYjffCju2eoP/jc/RJPqZuSg4E76bo+m1gSt > kPlkEiqzzqMJk9oAJIzBBKHY1ySgDxETjpikI6AdYqnB4rCZFJKOcAA2yRm1GOEW > adFg3dc6k4WhjhvOU5jfZyiQzaEXxAN7xWBy8Lwx7z5/+A1ewmXzsD6lUTLrOYIM > FDDIYHCayIxPPlQXQgI1o8ZFd8o6jNUkpHXFNE3sA6RFviQHbNVd5WTs1260qRsm > zlI5shT+82jCUQOZZZ/HaJQTA3FJhvskrYJ365NJ5ieuK62o1jWT7eoUDSq34JSX > x8yuOg0yA168qBzjjsj0zpDiWnCxuMVnF4ZGjEZKmribHSuMX+RKSWY5RTvr/3xe > BQMVFijvTemXGPLFXgemZxNW3HIqyu4ZmIZTgiNNCoikJ3/9gZtGKU1CHJXDM31G > onuaxDbfQeQNBqudL3DNUk9qUjXxLXSLFFqpSzEIoAZKFckVDsUwoDCvWyV5AtCK > +JRt0QSf8I/pRBxyPSkOPSsB9/JJEfndjE67YZgiObKsBF4A24Gg3acP+sRyRXnp > rNJxIzYWZkXg3ZUonHxzK42qEEnh5v4l8Qpp1ckboRKWyfgaamHrnqIvRQ4DF+Fz > bCTZZDn7SWqVsat6kpLVbivqoalh2iCYrVG8IdcW8F6nV1pdB0JPTmDMKjv0nCQP > UCqy65k6vOnAHgTx3mT0 > =wG6/ > -----END PGP SIGNATURE----- > > _______________________________________________ > 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 Apr 15 12:30:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Apr 2015 12:30:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YiMSp-0000TW-CX; Wed, 15 Apr 2015 12:30:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YiMSo-0000Sp-HL for mirageos-devel@lists.xenproject.org; Wed, 15 Apr 2015 12:30:42 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id FD/C7-05046-1F95E255; Wed, 15 Apr 2015 12:30:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1429101040!18141058!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP, UPPERCASE_25_50 X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23806 invoked from network); 15 Apr 2015 12:30:40 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Apr 2015 12:30:40 -0000 Received: from [IPv6:::1] (localhost [127.0.0.1]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 63b6a4fa; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 15 Apr 2015 13:30:39 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <552D20C3.5020102@mehnert.org> Date: Wed, 15 Apr 2015 13:30:40 +0100 Message-Id: References: <552D20C3.5020102@mehnert.org> To: Hannes Mehnert , Yaron Minsky X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TLS tunnel 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 Looks great! I've created a few issues that would be useful to fix before putting this into production use. I'm going to deploy this to replace stud on https://realworldocaml.org shortly... Anil > On 14 Apr 2015, at 15:14, Hannes Mehnert wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > I wrote a small Unix application, which is very similar to the popular > stunnel tool (and should be a dropin replacement for many use cases). > It uses our OCaml-TLS library. > > TLS Tunnel listens on a given port for TLS connections, and forwards the > unencrypted connection to a given destination on destination port. It > can also write a logfile. > > It currently uses lwt (no mirage yet [waiting for merges]). If you > want to try it out, get it at https://github.com/hannesm/tlstunnel > > or opam pin add tlstunnel https://github.com/hannesm/tlstunnel > > > If you have any questions or find issues, please let me know via the > issue tracker, > > hannes > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCQAGBQJVLSDDAAoJELyJZYjffCju2eoP/jc/RJPqZuSg4E76bo+m1gSt > kPlkEiqzzqMJk9oAJIzBBKHY1ySgDxETjpikI6AdYqnB4rCZFJKOcAA2yRm1GOEW > adFg3dc6k4WhjhvOU5jfZyiQzaEXxAN7xWBy8Lwx7z5/+A1ewmXzsD6lUTLrOYIM > FDDIYHCayIxPPlQXQgI1o8ZFd8o6jNUkpHXFNE3sA6RFviQHbNVd5WTs1260qRsm > zlI5shT+82jCUQOZZZ/HaJQTA3FJhvskrYJ365NJ5ieuK62o1jWT7eoUDSq34JSX > x8yuOg0yA168qBzjjsj0zpDiWnCxuMVnF4ZGjEZKmribHSuMX+RKSWY5RTvr/3xe > BQMVFijvTemXGPLFXgemZxNW3HIqyu4ZmIZTgiNNCoikJ3/9gZtGKU1CHJXDM31G > onuaxDbfQeQNBqudL3DNUk9qUjXxLXSLFFqpSzEIoAZKFckVDsUwoDCvWyV5AtCK > +JRt0QSf8I/pRBxyPSkOPSsB9/JJEfndjE67YZgiObKsBF4A24Gg3acP+sRyRXnp > rNJxIzYWZkXg3ZUonHxzK42qEEnh5v4l8Qpp1ckboRKWyfgaamHrnqIvRQ4DF+Fz > bCTZZDn7SWqVsat6kpLVbivqoalh2iCYrVG8IdcW8F6nV1pdB0JPTmDMKjv0nCQP > UCqy65k6vOnAHgTx3mT0 > =wG6/ > -----END PGP SIGNATURE----- > > _______________________________________________ > 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 Thu Apr 16 23:03:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 16 Apr 2015 23:03: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 1YisoB-0007nm-OK; Thu, 16 Apr 2015 23:02:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YisoA-0007nh-Ka for mirageos-devel@lists.xenproject.org; Thu, 16 Apr 2015 23:02:54 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 4D/9C-26324-D9F30355; Thu, 16 Apr 2015 23:02:53 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1429225373!17261160!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10572 invoked from network); 16 Apr 2015 23:02:53 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Apr 2015 23:02:53 -0000 Received: by widjs5 with SMTP id js5so21949705wid.1 for ; Thu, 16 Apr 2015 16:02:52 -0700 (PDT) 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=qpZteEBTsw28frWGGiQr8c3jC93kHcPbHfgejzFsiyk=; b=ry/VVyA29mdweYardR0KChUGijqIBWfVPzkqnwIIeNSXCUMqtjOi30g/rKntPtRvsC leFMYhtuOX2EDksN0JR+j9zjE0p9+k41djpZU0CzdBQPJZEPsXN5OwQZdLKtnhB0hJAJ Mutu78AQTN68NiPtC42FI7MYwOsQRyA60pB2YTLwN+5wMuJhM8kZPwCxvO5IVoi8YwDI VAvcwRsGYTZwXe0kUTkbZki2tlXG9fKtoyTh2ID7dQxc/f5CeimsICO5vNoM9Y3iDUq2 hcSV2Z1QAQVyMh0ZCe2kisiOyEJiBbiMUb8QdjAwla+gjFIU/WAchddFiDPMVhjrzACO sr/g== X-Received: by 10.194.187.16 with SMTP id fo16mr236136wjc.86.1429225372768; Thu, 16 Apr 2015 16:02:52 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id xy2sm12205684wjc.14.2015.04.16.16.02.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 Apr 2015 16:02:51 -0700 (PDT) From: Thomas Gazagnaire Message-Id: Date: Fri, 17 Apr 2015 00:02:52 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] [ANN] release of Mirage 2.4.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="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org SGksCgpJJ3ZlIGp1c3QgcmVsZWFzZWQgbWlyYWdlIDIuNC4wIGluIG9wYW0sIHdoaWNoIGdvZXMg dG9nZXRoZXIgd2l0aCBjb25kdWl0IDAuOC4wLCBtaXJhZ2UtY29uZHVpdC4yLjEuMCwgdGNwaXAu Mi40LjAgYW5kIG1pcmFnZS1odHRwLjIuMi4wLiBUaGVzZSByZWxlYXNlcyBpbXByb3ZlIHRoZSBU TFMgc3VwcG9ydCwgZml4IEFSUCBpc3N1ZXMsIG1ha2UgdGhlIG1pcmFnZSBIVFRQIHNlcnZlciBz aWduYXR1cmUgb25seSBkZXBlbmQgb24gVjEuRkxPVyBhbmQgZml4IHNvbWUgdXNhYmlsaXR5IGlz c3VlcyB3aXRoIHRoZSBtaXJhZ2UgY29tbWFuZC1saW5lIHRvb2wuCgpUaGUgZnVsbCBjaGFuZ2Vs b2c6CgojIyBjb25kdWl0IDAuOC4wCgrigKIgQWRkIFRMUyBjbGllbnQgc3VwcG9ydCBmb3IgTWly YWdlICgjNTApCuKAoiBEbyBub3Qgb3ZlcndyaXRlIHRoZSBkZWZhdWx0IG5hbWUgcmVzb2x2ZXIg Zm9yIE1pcmFnZSAoIzQ5KQrigKIgQWRkIFRMUyBzdXBwb3J0IHVzaW5nIHRoZSBwdXJlIE9DYW1s IFRMUyBzdGFjayAoIzQ2KS4K4oCiIFJlcGxhY2UgdGhlIE1pcmFnZSBNYWtlX2Zsb3cgZnVuY3Rv ciB3aXRoIER5bmFtaWNfZmxvdyB0aGF0IGlzIGVhc2llciB0byBleHRlbmQgd2l0aCBtb3JlIGZs b3cgdHlwZXMuCgojIyB0Y3BpcCAyLjQuMAoK4oCiIEFSUCBpbXByb3ZlbWVudHMgKCMxMTgpCgoj IyBtaXJhZ2UtaHR0cCAyLjIuMAoK4oCiIERvIG5vdCB1c2VyIGx3dC5zeW50YXgK4oCiIFJlbmFt ZSBIVFRQIHRvIENvaHR0cF9taXJhZ2UgKCM5KQrigKIgRXhwb3NlIENvaHR0cF9taXJhZ2VfaW8K 4oCiIEV4cG9zZSBhIFNlcnZlciBmdW5jdG9yIHdoaWNoIGRlcGVuZHMgb25seSBvbiBtaXJhZ2Un cyBGTE9XIChubyBkZXBlbmRlbmN5IHRvIGNvbmR1aXQgYW55bW9yZSBpbiB0aGlzIGNhc2UpCuKA oiBNb2Rlcm5pemUgVHJhdmlzIENJIHNjcmlwdHMKCiMjIG1pcmFnZSAyLjQuMAoK4oCiIFN1cHBv cnQgbWlyYWdlLWh0dHAuMi4yLjAK4oCiIFN1cHBvcnQgY29uZHVpdC4wLjguMArigKIgU3VwcG9y dCB0Y3BpcC4yLjQuMArigKIgQWRkIHRpbWUgYW5kIGNsb2NrIHBhcmFtZXRlcnMgdG8gSVB2NCAo IzM2MiwgcGF0Y2ggZnJvbSBAeW9taW1vbm8pCuKAoiBTdXBwb3J0IGZvciBvY2FtbC10bHMgMC40 LjAuCuKAoiBDb25kdWl0IG5vdyB0YWtlcyBhbiBvcHRpb25hbCBUTFMgYXJndW1lbnQsIGFsbG93 aW5nIHNlcnZlcnMgdG8gc3VwcG9ydCBlbmNyeXB0aW9uLiAoIzM0NykK4oCiIEFkZCB0aGUgYWJp bGl0eSB0byBzcGVjaWZ5IE1ha2VmaWxlLnVzZXIgdG8gZXh0ZW5kIHRoZSBnZW5lcmF0ZWQgTWFr ZWZpbGUuIEFsc28gYWxsLGJ1aWxkIGFuZCBjbGVhbiBhcmUgbm93IGV4dGVuc2libGUgbWFrZSB0 YXJnZXRzLgrigKIgUmVtb3ZlIHRoZSBtaXJhZ2UgcnVuIGNvbW1hbmQgKCMzNzkpCuKAoiBDYWxs IG9wYW0gZGVwZXh0IHdoZW4gY29uZmlndXJpbmcgKCMzNzMpCuKAoiBBZGQgb3BhbSBmaWxlcyBm b3IgbWlyYWdlIGFuZCBtaXJhZ2UtdHlwZXMgcGFja2FnZXMK4oCiIEZpeCBtaXJhZ2UgLS12ZXJz aW9uICgjMzc0KQrigKIgQWRkIGEgdXBkYXRlLWRvYyB0YXJnZXQgdG8gdGhlIE1ha2VmaWxlIHRv IGVhc2lseSB1cGRhdGUgdGhlIG9ubGluZSBkb2N1bWVudGF0aW9uIGF0aHR0cDovL21pcmFnZS5n aXRodWIuaW8vbWlyYWdlLwoKQmVzdCwKVGhvbWFzCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VP Uy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Thu Apr 16 23:03:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 16 Apr 2015 23:03: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 1YisoB-0007nm-OK; Thu, 16 Apr 2015 23:02:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YisoA-0007nh-Ka for mirageos-devel@lists.xenproject.org; Thu, 16 Apr 2015 23:02:54 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 4D/9C-26324-D9F30355; Thu, 16 Apr 2015 23:02:53 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1429225373!17261160!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10572 invoked from network); 16 Apr 2015 23:02:53 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Apr 2015 23:02:53 -0000 Received: by widjs5 with SMTP id js5so21949705wid.1 for ; Thu, 16 Apr 2015 16:02:52 -0700 (PDT) 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=qpZteEBTsw28frWGGiQr8c3jC93kHcPbHfgejzFsiyk=; b=ry/VVyA29mdweYardR0KChUGijqIBWfVPzkqnwIIeNSXCUMqtjOi30g/rKntPtRvsC leFMYhtuOX2EDksN0JR+j9zjE0p9+k41djpZU0CzdBQPJZEPsXN5OwQZdLKtnhB0hJAJ Mutu78AQTN68NiPtC42FI7MYwOsQRyA60pB2YTLwN+5wMuJhM8kZPwCxvO5IVoi8YwDI VAvcwRsGYTZwXe0kUTkbZki2tlXG9fKtoyTh2ID7dQxc/f5CeimsICO5vNoM9Y3iDUq2 hcSV2Z1QAQVyMh0ZCe2kisiOyEJiBbiMUb8QdjAwla+gjFIU/WAchddFiDPMVhjrzACO sr/g== X-Received: by 10.194.187.16 with SMTP id fo16mr236136wjc.86.1429225372768; Thu, 16 Apr 2015 16:02:52 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id xy2sm12205684wjc.14.2015.04.16.16.02.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 Apr 2015 16:02:51 -0700 (PDT) From: Thomas Gazagnaire Message-Id: Date: Fri, 17 Apr 2015 00:02:52 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] [ANN] release of Mirage 2.4.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="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org SGksCgpJJ3ZlIGp1c3QgcmVsZWFzZWQgbWlyYWdlIDIuNC4wIGluIG9wYW0sIHdoaWNoIGdvZXMg dG9nZXRoZXIgd2l0aCBjb25kdWl0IDAuOC4wLCBtaXJhZ2UtY29uZHVpdC4yLjEuMCwgdGNwaXAu Mi40LjAgYW5kIG1pcmFnZS1odHRwLjIuMi4wLiBUaGVzZSByZWxlYXNlcyBpbXByb3ZlIHRoZSBU TFMgc3VwcG9ydCwgZml4IEFSUCBpc3N1ZXMsIG1ha2UgdGhlIG1pcmFnZSBIVFRQIHNlcnZlciBz aWduYXR1cmUgb25seSBkZXBlbmQgb24gVjEuRkxPVyBhbmQgZml4IHNvbWUgdXNhYmlsaXR5IGlz c3VlcyB3aXRoIHRoZSBtaXJhZ2UgY29tbWFuZC1saW5lIHRvb2wuCgpUaGUgZnVsbCBjaGFuZ2Vs b2c6CgojIyBjb25kdWl0IDAuOC4wCgrigKIgQWRkIFRMUyBjbGllbnQgc3VwcG9ydCBmb3IgTWly YWdlICgjNTApCuKAoiBEbyBub3Qgb3ZlcndyaXRlIHRoZSBkZWZhdWx0IG5hbWUgcmVzb2x2ZXIg Zm9yIE1pcmFnZSAoIzQ5KQrigKIgQWRkIFRMUyBzdXBwb3J0IHVzaW5nIHRoZSBwdXJlIE9DYW1s IFRMUyBzdGFjayAoIzQ2KS4K4oCiIFJlcGxhY2UgdGhlIE1pcmFnZSBNYWtlX2Zsb3cgZnVuY3Rv ciB3aXRoIER5bmFtaWNfZmxvdyB0aGF0IGlzIGVhc2llciB0byBleHRlbmQgd2l0aCBtb3JlIGZs b3cgdHlwZXMuCgojIyB0Y3BpcCAyLjQuMAoK4oCiIEFSUCBpbXByb3ZlbWVudHMgKCMxMTgpCgoj IyBtaXJhZ2UtaHR0cCAyLjIuMAoK4oCiIERvIG5vdCB1c2VyIGx3dC5zeW50YXgK4oCiIFJlbmFt ZSBIVFRQIHRvIENvaHR0cF9taXJhZ2UgKCM5KQrigKIgRXhwb3NlIENvaHR0cF9taXJhZ2VfaW8K 4oCiIEV4cG9zZSBhIFNlcnZlciBmdW5jdG9yIHdoaWNoIGRlcGVuZHMgb25seSBvbiBtaXJhZ2Un cyBGTE9XIChubyBkZXBlbmRlbmN5IHRvIGNvbmR1aXQgYW55bW9yZSBpbiB0aGlzIGNhc2UpCuKA oiBNb2Rlcm5pemUgVHJhdmlzIENJIHNjcmlwdHMKCiMjIG1pcmFnZSAyLjQuMAoK4oCiIFN1cHBv cnQgbWlyYWdlLWh0dHAuMi4yLjAK4oCiIFN1cHBvcnQgY29uZHVpdC4wLjguMArigKIgU3VwcG9y dCB0Y3BpcC4yLjQuMArigKIgQWRkIHRpbWUgYW5kIGNsb2NrIHBhcmFtZXRlcnMgdG8gSVB2NCAo IzM2MiwgcGF0Y2ggZnJvbSBAeW9taW1vbm8pCuKAoiBTdXBwb3J0IGZvciBvY2FtbC10bHMgMC40 LjAuCuKAoiBDb25kdWl0IG5vdyB0YWtlcyBhbiBvcHRpb25hbCBUTFMgYXJndW1lbnQsIGFsbG93 aW5nIHNlcnZlcnMgdG8gc3VwcG9ydCBlbmNyeXB0aW9uLiAoIzM0NykK4oCiIEFkZCB0aGUgYWJp bGl0eSB0byBzcGVjaWZ5IE1ha2VmaWxlLnVzZXIgdG8gZXh0ZW5kIHRoZSBnZW5lcmF0ZWQgTWFr ZWZpbGUuIEFsc28gYWxsLGJ1aWxkIGFuZCBjbGVhbiBhcmUgbm93IGV4dGVuc2libGUgbWFrZSB0 YXJnZXRzLgrigKIgUmVtb3ZlIHRoZSBtaXJhZ2UgcnVuIGNvbW1hbmQgKCMzNzkpCuKAoiBDYWxs IG9wYW0gZGVwZXh0IHdoZW4gY29uZmlndXJpbmcgKCMzNzMpCuKAoiBBZGQgb3BhbSBmaWxlcyBm b3IgbWlyYWdlIGFuZCBtaXJhZ2UtdHlwZXMgcGFja2FnZXMK4oCiIEZpeCBtaXJhZ2UgLS12ZXJz aW9uICgjMzc0KQrigKIgQWRkIGEgdXBkYXRlLWRvYyB0YXJnZXQgdG8gdGhlIE1ha2VmaWxlIHRv IGVhc2lseSB1cGRhdGUgdGhlIG9ubGluZSBkb2N1bWVudGF0aW9uIGF0aHR0cDovL21pcmFnZS5n aXRodWIuaW8vbWlyYWdlLwoKQmVzdCwKVGhvbWFzCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VP Uy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Fri Apr 17 07:18:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 07:18:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj0XP-0005sG-Gw; Fri, 17 Apr 2015 07:18:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj0XN-0005sB-Sf for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 07:18:05 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id 74/AC-07318-DA3B0355; Fri, 17 Apr 2015 07:18:05 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1429255084!17390163!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27316 invoked from network); 17 Apr 2015 07:18:04 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 07:18:04 -0000 Received: from [192.168.0.6] (cpc16-cmbg15-2-0-cust21.5-4.cable.virginm.net [86.5.162.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (not verified)) by mail.mehnert.org (Postfix) with ESMTPS id D7BB01B48 for ; Fri, 17 Apr 2015 09:18:02 +0200 (CEST) Message-ID: <5530B39F.2050802@mehnert.org> Date: Fri, 17 Apr 2015 08:17:51 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: In-Reply-To: OpenPGP: id=11B5464249B5BD858FFF6328BC896588DF7C28EE Subject: Re: [MirageOS-devel] [ANN] release of Mirage 2.4.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, On 04/17/2015 00:02, Thomas Gazagnaire wrote: > I've just released mirage 2.4.0 in opam, which goes together with > conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and > mirage-http.2.2.0. These releases improve the TLS support, fix ARP > issues, make the mirage HTTP server signature only depend on > V1.FLOW and fix some usability issues with the mirage command-line > tool. great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, namely not dealing well with trailing bytes, as described by Magnus Therning on this list. Also, the TLS/entropy story is not yet in its final shape (and will be improved on, see David Kaloper's thread 'update on entropy', and some discussion in https://github.com/mirage/mirage/pull/390). hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVMLOfAAoJELyJZYjffCjutvkP/AuvADIe3kPsJhEEHBcTyzdv md/vjgvtr4pVWVzRQb/nbYnCrCK8sElHoWuT2w4/YvSv6oMAOLpsMUHbjh1UzgH0 lHg+6UMjdLx5ukBveCRa/vpXiGDKNPS4zHX3bY0S98FPw/RdPVvBNh0gKn8Ykmxm qM5rmrbNwST+B6CPVeP623QFOGSjeOoSp3EyVh5don+8EkO4+oj5D6MVIAlqXVeK TPUczJjNJOMTW7VhJ8nEMXdGnainTF8nxQvKOObd8xiqNI9b0OFqRdahMsmYng4N WYriThYes/vepqtos8U7/7aJEsf3Mgw0WPyqKJmXcBolkEdL4nxjVDgh9jfxtAQo EkPYDZ6G2mVNtSPg12lVNcIUdnfsdNZ6ulQcGyXbOKJ6dDBPTjYPxav/yQ0EPG4w BL1G4lgujIDzO9Ef67t1dag1uwPnSgcmj7E/W7wz3xuZEmrZdIRMt6aVr2OthsSP U2oepc1bGHjW8RD2Vr6l/cgATCxd8tOpR1+Z04KdkU71tqdm0qCSQKoEvTGPRAkM D2tYaA7EJqI+L/OnfPLLzIDxdFelCDOJ8O+pN9bzP2truG108GSaccfQNr+yYNAy AY7eXYS+5zPD+EmBIya9FS0jmvzE7+ola0hEUOXmdJjRD9Sr7UydAZpmst/PLTM4 vD0wYq/vYHqWsCiF9PRe =6q3/ -----END PGP SIGNATURE----- _______________________________________________ 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 Apr 17 07:18:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 07:18:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj0XP-0005sG-Gw; Fri, 17 Apr 2015 07:18:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj0XN-0005sB-Sf for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 07:18:05 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id 74/AC-07318-DA3B0355; Fri, 17 Apr 2015 07:18:05 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1429255084!17390163!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27316 invoked from network); 17 Apr 2015 07:18:04 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 07:18:04 -0000 Received: from [192.168.0.6] (cpc16-cmbg15-2-0-cust21.5-4.cable.virginm.net [86.5.162.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (not verified)) by mail.mehnert.org (Postfix) with ESMTPS id D7BB01B48 for ; Fri, 17 Apr 2015 09:18:02 +0200 (CEST) Message-ID: <5530B39F.2050802@mehnert.org> Date: Fri, 17 Apr 2015 08:17:51 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: In-Reply-To: OpenPGP: id=11B5464249B5BD858FFF6328BC896588DF7C28EE Subject: Re: [MirageOS-devel] [ANN] release of Mirage 2.4.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, On 04/17/2015 00:02, Thomas Gazagnaire wrote: > I've just released mirage 2.4.0 in opam, which goes together with > conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and > mirage-http.2.2.0. These releases improve the TLS support, fix ARP > issues, make the mirage HTTP server signature only depend on > V1.FLOW and fix some usability issues with the mirage command-line > tool. great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, namely not dealing well with trailing bytes, as described by Magnus Therning on this list. Also, the TLS/entropy story is not yet in its final shape (and will be improved on, see David Kaloper's thread 'update on entropy', and some discussion in https://github.com/mirage/mirage/pull/390). hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCQAGBQJVMLOfAAoJELyJZYjffCjutvkP/AuvADIe3kPsJhEEHBcTyzdv md/vjgvtr4pVWVzRQb/nbYnCrCK8sElHoWuT2w4/YvSv6oMAOLpsMUHbjh1UzgH0 lHg+6UMjdLx5ukBveCRa/vpXiGDKNPS4zHX3bY0S98FPw/RdPVvBNh0gKn8Ykmxm qM5rmrbNwST+B6CPVeP623QFOGSjeOoSp3EyVh5don+8EkO4+oj5D6MVIAlqXVeK TPUczJjNJOMTW7VhJ8nEMXdGnainTF8nxQvKOObd8xiqNI9b0OFqRdahMsmYng4N WYriThYes/vepqtos8U7/7aJEsf3Mgw0WPyqKJmXcBolkEdL4nxjVDgh9jfxtAQo EkPYDZ6G2mVNtSPg12lVNcIUdnfsdNZ6ulQcGyXbOKJ6dDBPTjYPxav/yQ0EPG4w BL1G4lgujIDzO9Ef67t1dag1uwPnSgcmj7E/W7wz3xuZEmrZdIRMt6aVr2OthsSP U2oepc1bGHjW8RD2Vr6l/cgATCxd8tOpR1+Z04KdkU71tqdm0qCSQKoEvTGPRAkM D2tYaA7EJqI+L/OnfPLLzIDxdFelCDOJ8O+pN9bzP2truG108GSaccfQNr+yYNAy AY7eXYS+5zPD+EmBIya9FS0jmvzE7+ola0hEUOXmdJjRD9Sr7UydAZpmst/PLTM4 vD0wYq/vYHqWsCiF9PRe =6q3/ -----END PGP SIGNATURE----- _______________________________________________ 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 Apr 17 07:22:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 07:22: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 1Yj0bP-000634-Su; Fri, 17 Apr 2015 07:22:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj0bO-00062z-RY for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 07:22:14 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 43/BB-27592-6A4B0355; Fri, 17 Apr 2015 07:22:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1429255333!13215863!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20584 invoked from network); 17 Apr 2015 07:22:13 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 07:22:13 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 198bdc8d; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 08:22:12 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5530B39F.2050802@mehnert.org> Date: Fri, 17 Apr 2015 08:22:11 +0100 Message-Id: <05DC9633-3B64-4E12-B958-820C30B6D086@recoil.org> References: <5530B39F.2050802@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] [ANN] release of Mirage 2.4.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 On 17 Apr 2015, at 08:17, Hannes Mehnert wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > On 04/17/2015 00:02, Thomas Gazagnaire wrote: >> I've just released mirage 2.4.0 in opam, which goes together with >> conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and >> mirage-http.2.2.0. These releases improve the TLS support, fix ARP >> issues, make the mirage HTTP server signature only depend on >> V1.FLOW and fix some usability issues with the mirage command-line >> tool. > > great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, > namely not dealing well with trailing bytes, as described by Magnus > Therning on this list. I'll deal with this one today... I'm recompiling my ARM setup right now. > Also, the TLS/entropy story is not yet in its final shape (and will be > improved on, see David Kaloper's thread 'update on entropy', and some > discussion in https://github.com/mirage/mirage/pull/390). Absolutely; 2.4.0 is an intermediate release to get some of the interface changes required unblocked, but is not the 'supported' SSL release yet. 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 Apr 17 07:22:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 07:22: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 1Yj0bP-000634-Su; Fri, 17 Apr 2015 07:22:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj0bO-00062z-RY for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 07:22:14 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 43/BB-27592-6A4B0355; Fri, 17 Apr 2015 07:22:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1429255333!13215863!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20584 invoked from network); 17 Apr 2015 07:22:13 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 07:22:13 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 198bdc8d; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 08:22:12 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5530B39F.2050802@mehnert.org> Date: Fri, 17 Apr 2015 08:22:11 +0100 Message-Id: <05DC9633-3B64-4E12-B958-820C30B6D086@recoil.org> References: <5530B39F.2050802@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] [ANN] release of Mirage 2.4.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 On 17 Apr 2015, at 08:17, Hannes Mehnert wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > On 04/17/2015 00:02, Thomas Gazagnaire wrote: >> I've just released mirage 2.4.0 in opam, which goes together with >> conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and >> mirage-http.2.2.0. These releases improve the TLS support, fix ARP >> issues, make the mirage HTTP server signature only depend on >> V1.FLOW and fix some usability issues with the mirage command-line >> tool. > > great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, > namely not dealing well with trailing bytes, as described by Magnus > Therning on this list. I'll deal with this one today... I'm recompiling my ARM setup right now. > Also, the TLS/entropy story is not yet in its final shape (and will be > improved on, see David Kaloper's thread 'update on entropy', and some > discussion in https://github.com/mirage/mirage/pull/390). Absolutely; 2.4.0 is an intermediate release to get some of the interface changes required unblocked, but is not the 'supported' SSL release yet. 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 Apr 17 10:51:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 10:51: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 1Yj3sG-0008Nv-NV; Fri, 17 Apr 2015 10:51:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj3sF-0008Nd-8P for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 10:51:51 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id EA/E7-31676-6C5E0355; Fri, 17 Apr 2015 10:51:50 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-3.tower-27.messagelabs.com!1429267907!15330558!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26694 invoked from network); 17 Apr 2015 10:51:48 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 10:51:48 -0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0A1B020AA7 for ; Fri, 17 Apr 2015 06:51:47 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute4.internal (MEProxy); Fri, 17 Apr 2015 06:51:47 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=Mdm vJe2DEsqMBDcJlvhvCMUHdyc=; b=l1hBGSvvWnm3tGTkrpxpvFA0TsIGLn+J7BD R628+UO8woX+mUjddE5b68QLFoiqCz8D9QUoeJfoaEwDOA4hZeZhEDiOKNCTv+Gu k6B6f9PRoQ+7VdvKO8HiiD1XvsATR6QdY9r6clOicPaDhcw4hock/i4h1Tsv+7/W SndLxB+k= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=MdmvJe2DEsqMBDcJlvhvCMUHdyc=; b=sbU6i kjOur9WAdClLyETDZymz68l+bcKTRlpqprNu1/FsWGekUriuU61NUEkgVY2r1vgE bLmwP2LmfDuMQpeGEUsL3EIls1aU2IWT9uPIAevrV/o2RowMBFqY3VMBXGpDyvIq WccBosFPWegxu+LBkJMD7pz5+5IOvQJXER5j4A= Received: by web1.nyi.internal (Postfix, from userid 99) id D16C2AF2D0F; Fri, 17 Apr 2015 06:51:46 -0400 (EDT) Message-Id: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> X-Sasl-Enc: j4UbuJoBymnjq1rbCU+IYYDXao4rcLKlA0OEmUQ+dqQ5 1429267906 From: Magnus Skjegstad To: mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-424f40c2 Date: Fri, 17 Apr 2015 11:51:46 +0100 Subject: [MirageOS-devel] Unikernel/Xen server hosting 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 have been looking for a place to run a Xen server where I can run MirageOS unikernels and Scaleway [1] looks like it could be a good and reasonably priced option. Has anyone had any experience with them or been able to successfully install Xen there? 1. https://www.scaleway.com -- Magnus _______________________________________________ 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 Apr 17 10:51:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 10:51: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 1Yj3sG-0008Nv-NV; Fri, 17 Apr 2015 10:51:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj3sF-0008Nd-8P for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 10:51:51 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id EA/E7-31676-6C5E0355; Fri, 17 Apr 2015 10:51:50 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-3.tower-27.messagelabs.com!1429267907!15330558!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26694 invoked from network); 17 Apr 2015 10:51:48 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 10:51:48 -0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0A1B020AA7 for ; Fri, 17 Apr 2015 06:51:47 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute4.internal (MEProxy); Fri, 17 Apr 2015 06:51:47 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=Mdm vJe2DEsqMBDcJlvhvCMUHdyc=; b=l1hBGSvvWnm3tGTkrpxpvFA0TsIGLn+J7BD R628+UO8woX+mUjddE5b68QLFoiqCz8D9QUoeJfoaEwDOA4hZeZhEDiOKNCTv+Gu k6B6f9PRoQ+7VdvKO8HiiD1XvsATR6QdY9r6clOicPaDhcw4hock/i4h1Tsv+7/W SndLxB+k= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=MdmvJe2DEsqMBDcJlvhvCMUHdyc=; b=sbU6i kjOur9WAdClLyETDZymz68l+bcKTRlpqprNu1/FsWGekUriuU61NUEkgVY2r1vgE bLmwP2LmfDuMQpeGEUsL3EIls1aU2IWT9uPIAevrV/o2RowMBFqY3VMBXGpDyvIq WccBosFPWegxu+LBkJMD7pz5+5IOvQJXER5j4A= Received: by web1.nyi.internal (Postfix, from userid 99) id D16C2AF2D0F; Fri, 17 Apr 2015 06:51:46 -0400 (EDT) Message-Id: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> X-Sasl-Enc: j4UbuJoBymnjq1rbCU+IYYDXao4rcLKlA0OEmUQ+dqQ5 1429267906 From: Magnus Skjegstad To: mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-424f40c2 Date: Fri, 17 Apr 2015 11:51:46 +0100 Subject: [MirageOS-devel] Unikernel/Xen server hosting 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 have been looking for a place to run a Xen server where I can run MirageOS unikernels and Scaleway [1] looks like it could be a good and reasonably priced option. Has anyone had any experience with them or been able to successfully install Xen there? 1. https://www.scaleway.com -- Magnus _______________________________________________ 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 Apr 17 11:00:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 11:00: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 1Yj40i-00018Q-Es; Fri, 17 Apr 2015 11:00:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj40h-00018I-6Q for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 11:00:35 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 1A/4E-26324-2D7E0355; Fri, 17 Apr 2015 11:00:34 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1429268432!17473210!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18960 invoked from network); 17 Apr 2015 11:00:32 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 11:00:32 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id f20caf1b; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 12:00:32 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> Date: Fri, 17 Apr 2015 12:00:31 +0100 Message-Id: <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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 Apr 2015, at 11:51, Magnus Skjegstad wrote: > > I have been looking for a place to run a Xen server where I can run > MirageOS unikernels and Scaleway [1] looks like it could be a good and > reasonably priced option. Has anyone had any experience with them or > been able to successfully install Xen there? > > 1. https://www.scaleway.com I've been running on Scaleway since its closed beta, and it definitely has a lot of potential for us! Some notes: - They have a Docker/ARM image which I'm using. I've successfully modified my ocaml-docker-scripts (that drive the bulk builds at http://opam.ocaml.org/builds) to build ARM images for Ubuntu. Not done any more than play with it, but I think it could be integrated to give us x86 and ARM bulk builds without the hassle of having our local ARM clusters burn up from the heat :) - There's an open issue: https://github.com/scaleway/kernel-tools/issues/14 regarding getting a Xen-compatible kernel there, so I've asked about progress. - In the meanwhile though, it works great for userspace builds of Xen/ARM kernels, so it could be a good place to augment mirage-www's deployment scripts to also build ARM images as well as x86. This requires David Sheets' GitHub watcher which is making fast progress. It might also be interesting to run a Jitsu daemon on them in "userspace" with a Mirage tuntap Unix binary. -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 Apr 17 11:00:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 11:00: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 1Yj40i-00018Q-Es; Fri, 17 Apr 2015 11:00:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj40h-00018I-6Q for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 11:00:35 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 1A/4E-26324-2D7E0355; Fri, 17 Apr 2015 11:00:34 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1429268432!17473210!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18960 invoked from network); 17 Apr 2015 11:00:32 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 11:00:32 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id f20caf1b; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 12:00:32 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> Date: Fri, 17 Apr 2015 12:00:31 +0100 Message-Id: <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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 Apr 2015, at 11:51, Magnus Skjegstad wrote: > > I have been looking for a place to run a Xen server where I can run > MirageOS unikernels and Scaleway [1] looks like it could be a good and > reasonably priced option. Has anyone had any experience with them or > been able to successfully install Xen there? > > 1. https://www.scaleway.com I've been running on Scaleway since its closed beta, and it definitely has a lot of potential for us! Some notes: - They have a Docker/ARM image which I'm using. I've successfully modified my ocaml-docker-scripts (that drive the bulk builds at http://opam.ocaml.org/builds) to build ARM images for Ubuntu. Not done any more than play with it, but I think it could be integrated to give us x86 and ARM bulk builds without the hassle of having our local ARM clusters burn up from the heat :) - There's an open issue: https://github.com/scaleway/kernel-tools/issues/14 regarding getting a Xen-compatible kernel there, so I've asked about progress. - In the meanwhile though, it works great for userspace builds of Xen/ARM kernels, so it could be a good place to augment mirage-www's deployment scripts to also build ARM images as well as x86. This requires David Sheets' GitHub watcher which is making fast progress. It might also be interesting to run a Jitsu daemon on them in "userspace" with a Mirage tuntap Unix binary. -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 Apr 17 14:50:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 14:50:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7bJ-00017g-JP; Fri, 17 Apr 2015 14:50:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7bI-00017Q-4Z for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 14:50:36 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id F7/67-19899-BBD11355; Fri, 17 Apr 2015 14:50:35 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1429282234!16750970!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8264 invoked from network); 17 Apr 2015 14:50:34 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 14:50:34 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcpprivate4449.jbs.private.cam.ac.uk ([172.25.125.195]:64553) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Yj7bF-00034R-rs (Exim 4.82_3-c0e5623) (return-path ); Fri, 17 Apr 2015 15:50:33 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> Date: Fri, 17 Apr 2015 15:50:35 +0100 Message-Id: References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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 Apr 2015, at 12:00, Anil Madhavapeddy wrote: > - In the meanwhile though, it works great for userspace builds of > Xen/ARM kernels, so it could be a good place to augment mirage-www's > deployment scripts to also build ARM images as well as x86. This > requires David Sheets' GitHub watcher which is making fast progress. > It might also be interesting to run a Jitsu daemon on them in > "userspace" with a Mirage tuntap Unix binary Sounds like we could use Scaleway's cloud to automate build and deployments to cubieboards (in a similar way to how we use Travis and GitHub right now [1, 2]). Am I right? That would be really cool and mitigate some of the issues around cross-compliation. Amir [1] http://amirchaudhry.com/from-jekyll-to-unikernel-in-fifty-lines/ [2] http://amirchaudhry.com/heroku-for-unikernels-pt1/ _______________________________________________ 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 Apr 17 14:50:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 14:50:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7bJ-00017g-JP; Fri, 17 Apr 2015 14:50:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7bI-00017Q-4Z for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 14:50:36 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id F7/67-19899-BBD11355; Fri, 17 Apr 2015 14:50:35 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1429282234!16750970!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8264 invoked from network); 17 Apr 2015 14:50:34 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 14:50:34 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcpprivate4449.jbs.private.cam.ac.uk ([172.25.125.195]:64553) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Yj7bF-00034R-rs (Exim 4.82_3-c0e5623) (return-path ); Fri, 17 Apr 2015 15:50:33 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> Date: Fri, 17 Apr 2015 15:50:35 +0100 Message-Id: References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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 Apr 2015, at 12:00, Anil Madhavapeddy wrote: > - In the meanwhile though, it works great for userspace builds of > Xen/ARM kernels, so it could be a good place to augment mirage-www's > deployment scripts to also build ARM images as well as x86. This > requires David Sheets' GitHub watcher which is making fast progress. > It might also be interesting to run a Jitsu daemon on them in > "userspace" with a Mirage tuntap Unix binary Sounds like we could use Scaleway's cloud to automate build and deployments to cubieboards (in a similar way to how we use Travis and GitHub right now [1, 2]). Am I right? That would be really cool and mitigate some of the issues around cross-compliation. Amir [1] http://amirchaudhry.com/from-jekyll-to-unikernel-in-fifty-lines/ [2] http://amirchaudhry.com/heroku-for-unikernels-pt1/ _______________________________________________ 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 Apr 17 14:52:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 14:52:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7dH-0001Ct-RT; Fri, 17 Apr 2015 14:52:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7dG-0001Ci-0K for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 14:52:38 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 3C/FA-02119-53E11355; Fri, 17 Apr 2015 14:52:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-206.messagelabs.com!1429282356!13879328!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7974 invoked from network); 17 Apr 2015 14:52:36 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 14:52:36 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 00945196; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 15:52:36 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 17 Apr 2015 15:52:35 +0100 Message-Id: References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> To: Amir M Chaudhry X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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 Apr 2015, at 15:50, Amir Chaudhry wrote: > > > On 17 Apr 2015, at 12:00, Anil Madhavapeddy wrote: > >> - In the meanwhile though, it works great for userspace builds of >> Xen/ARM kernels, so it could be a good place to augment mirage-www's >> deployment scripts to also build ARM images as well as x86. This >> requires David Sheets' GitHub watcher which is making fast progress. >> It might also be interesting to run a Jitsu daemon on them in >> "userspace" with a Mirage tuntap Unix binary > > Sounds like we could use Scaleway's cloud to automate build and deployments to cubieboards (in a similar way to how we use Travis and GitHub right now [1, 2]). Am I right? That would be really cool and mitigate some of the issues around cross-compliation. Yep, that's right. They build the same ARMv7 kernels as a Cubieboard does today. -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 Apr 17 14:52:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 14:52:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7dH-0001Ct-RT; Fri, 17 Apr 2015 14:52:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj7dG-0001Ci-0K for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 14:52:38 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 3C/FA-02119-53E11355; Fri, 17 Apr 2015 14:52:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-206.messagelabs.com!1429282356!13879328!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7974 invoked from network); 17 Apr 2015 14:52:36 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 14:52:36 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 00945196; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 15:52:36 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 17 Apr 2015 15:52:35 +0100 Message-Id: References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> To: Amir M Chaudhry X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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 Apr 2015, at 15:50, Amir Chaudhry wrote: > > > On 17 Apr 2015, at 12:00, Anil Madhavapeddy wrote: > >> - In the meanwhile though, it works great for userspace builds of >> Xen/ARM kernels, so it could be a good place to augment mirage-www's >> deployment scripts to also build ARM images as well as x86. This >> requires David Sheets' GitHub watcher which is making fast progress. >> It might also be interesting to run a Jitsu daemon on them in >> "userspace" with a Mirage tuntap Unix binary > > Sounds like we could use Scaleway's cloud to automate build and deployments to cubieboards (in a similar way to how we use Travis and GitHub right now [1, 2]). Am I right? That would be really cool and mitigate some of the issues around cross-compliation. Yep, that's right. They build the same ARMv7 kernels as a Cubieboard does today. -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 Apr 17 17:11:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 17:11: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 1Yj9nw-00033S-IK; Fri, 17 Apr 2015 17:11:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj9nu-00032o-TE for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 17:11:47 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 65/F0-20070-2DE31355; Fri, 17 Apr 2015 17:11:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-206.messagelabs.com!1429290704!16830774!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32251 invoked from network); 17 Apr 2015 17:11:45 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-7.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 17:11:45 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 36ff6b52; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 18:11:44 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 17 Apr 2015 18:11:43 +0100 Message-Id: <056177E3-7636-4779-AA21-16741936A080@recoil.org> References: <552D20C3.5020102@mehnert.org> To: Hannes Mehnert , Yaron Minsky X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TLS tunnel 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 After a few minor fixes for SIGPIPE and such (all included in the tlstunnel repo upstream), it's serving https://realworldocaml.org! It's marked as an A- in the SSLTester website due to us still using a SHA1 certificate. I'll regenerate it with Gandi to SHA2 later on, but for now if everyone could point their weirdest browsers at realworldocaml.org and report any problems with accessing it, that would be appreciated! -anil > On 15 Apr 2015, at 13:30, Anil Madhavapeddy wrote: > > Looks great! I've created a few issues that would be useful to fix > before putting this into production use. I'm going to deploy this > to replace stud on https://realworldocaml.org shortly... > > Anil > >> On 14 Apr 2015, at 15:14, Hannes Mehnert wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA384 >> >> Hi, >> >> I wrote a small Unix application, which is very similar to the popular >> stunnel tool (and should be a dropin replacement for many use cases). >> It uses our OCaml-TLS library. >> >> TLS Tunnel listens on a given port for TLS connections, and forwards the >> unencrypted connection to a given destination on destination port. It >> can also write a logfile. >> >> It currently uses lwt (no mirage yet [waiting for merges]). If you >> want to try it out, get it at https://github.com/hannesm/tlstunnel >> >> or opam pin add tlstunnel https://github.com/hannesm/tlstunnel >> >> >> If you have any questions or find issues, please let me know via the >> issue tracker, >> >> hannes >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2 >> >> iQIcBAEBCQAGBQJVLSDDAAoJELyJZYjffCju2eoP/jc/RJPqZuSg4E76bo+m1gSt >> kPlkEiqzzqMJk9oAJIzBBKHY1ySgDxETjpikI6AdYqnB4rCZFJKOcAA2yRm1GOEW >> adFg3dc6k4WhjhvOU5jfZyiQzaEXxAN7xWBy8Lwx7z5/+A1ewmXzsD6lUTLrOYIM >> FDDIYHCayIxPPlQXQgI1o8ZFd8o6jNUkpHXFNE3sA6RFviQHbNVd5WTs1260qRsm >> zlI5shT+82jCUQOZZZ/HaJQTA3FJhvskrYJ365NJ5ieuK62o1jWT7eoUDSq34JSX >> x8yuOg0yA168qBzjjsj0zpDiWnCxuMVnF4ZGjEZKmribHSuMX+RKSWY5RTvr/3xe >> BQMVFijvTemXGPLFXgemZxNW3HIqyu4ZmIZTgiNNCoikJ3/9gZtGKU1CHJXDM31G >> onuaxDbfQeQNBqudL3DNUk9qUjXxLXSLFFqpSzEIoAZKFckVDsUwoDCvWyV5AtCK >> +JRt0QSf8I/pRBxyPSkOPSsB9/JJEfndjE67YZgiObKsBF4A24Gg3acP+sRyRXnp >> rNJxIzYWZkXg3ZUonHxzK42qEEnh5v4l8Qpp1ckboRKWyfgaamHrnqIvRQ4DF+Fz >> bCTZZDn7SWqVsat6kpLVbivqoalh2iCYrVG8IdcW8F6nV1pdB0JPTmDMKjv0nCQP >> UCqy65k6vOnAHgTx3mT0 >> =wG6/ >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> 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 Fri Apr 17 17:11:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 17:11: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 1Yj9nw-00033S-IK; Fri, 17 Apr 2015 17:11:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yj9nu-00032o-TE for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 17:11:47 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 65/F0-20070-2DE31355; Fri, 17 Apr 2015 17:11:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-206.messagelabs.com!1429290704!16830774!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32251 invoked from network); 17 Apr 2015 17:11:45 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-7.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 17:11:45 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 36ff6b52; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 17 Apr 2015 18:11:44 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 17 Apr 2015 18:11:43 +0100 Message-Id: <056177E3-7636-4779-AA21-16741936A080@recoil.org> References: <552D20C3.5020102@mehnert.org> To: Hannes Mehnert , Yaron Minsky X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TLS tunnel 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 After a few minor fixes for SIGPIPE and such (all included in the tlstunnel repo upstream), it's serving https://realworldocaml.org! It's marked as an A- in the SSLTester website due to us still using a SHA1 certificate. I'll regenerate it with Gandi to SHA2 later on, but for now if everyone could point their weirdest browsers at realworldocaml.org and report any problems with accessing it, that would be appreciated! -anil > On 15 Apr 2015, at 13:30, Anil Madhavapeddy wrote: > > Looks great! I've created a few issues that would be useful to fix > before putting this into production use. I'm going to deploy this > to replace stud on https://realworldocaml.org shortly... > > Anil > >> On 14 Apr 2015, at 15:14, Hannes Mehnert wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA384 >> >> Hi, >> >> I wrote a small Unix application, which is very similar to the popular >> stunnel tool (and should be a dropin replacement for many use cases). >> It uses our OCaml-TLS library. >> >> TLS Tunnel listens on a given port for TLS connections, and forwards the >> unencrypted connection to a given destination on destination port. It >> can also write a logfile. >> >> It currently uses lwt (no mirage yet [waiting for merges]). If you >> want to try it out, get it at https://github.com/hannesm/tlstunnel >> >> or opam pin add tlstunnel https://github.com/hannesm/tlstunnel >> >> >> If you have any questions or find issues, please let me know via the >> issue tracker, >> >> hannes >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2 >> >> iQIcBAEBCQAGBQJVLSDDAAoJELyJZYjffCju2eoP/jc/RJPqZuSg4E76bo+m1gSt >> kPlkEiqzzqMJk9oAJIzBBKHY1ySgDxETjpikI6AdYqnB4rCZFJKOcAA2yRm1GOEW >> adFg3dc6k4WhjhvOU5jfZyiQzaEXxAN7xWBy8Lwx7z5/+A1ewmXzsD6lUTLrOYIM >> FDDIYHCayIxPPlQXQgI1o8ZFd8o6jNUkpHXFNE3sA6RFviQHbNVd5WTs1260qRsm >> zlI5shT+82jCUQOZZZ/HaJQTA3FJhvskrYJ365NJ5ieuK62o1jWT7eoUDSq34JSX >> x8yuOg0yA168qBzjjsj0zpDiWnCxuMVnF4ZGjEZKmribHSuMX+RKSWY5RTvr/3xe >> BQMVFijvTemXGPLFXgemZxNW3HIqyu4ZmIZTgiNNCoikJ3/9gZtGKU1CHJXDM31G >> onuaxDbfQeQNBqudL3DNUk9qUjXxLXSLFFqpSzEIoAZKFckVDsUwoDCvWyV5AtCK >> +JRt0QSf8I/pRBxyPSkOPSsB9/JJEfndjE67YZgiObKsBF4A24Gg3acP+sRyRXnp >> rNJxIzYWZkXg3ZUonHxzK42qEEnh5v4l8Qpp1ckboRKWyfgaamHrnqIvRQ4DF+Fz >> bCTZZDn7SWqVsat6kpLVbivqoalh2iCYrVG8IdcW8F6nV1pdB0JPTmDMKjv0nCQP >> UCqy65k6vOnAHgTx3mT0 >> =wG6/ >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> 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 Fri Apr 17 20:50:07 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 20:50:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjDD5-0005DB-79; Fri, 17 Apr 2015 20:49:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjDD3-0005D2-NJ for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 20:49:57 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id DB/E7-14975-4F171355; Fri, 17 Apr 2015 20:49:56 +0000 X-Env-Sender: nick@internetmachines.co.uk X-Msg-Ref: server-12.tower-31.messagelabs.com!1429303789!17536503!1 X-Originating-IP: [213.138.108.180] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31531 invoked from network); 17 Apr 2015 20:49:49 -0000 Received: from adm02.default.planetlarg.uk0.bigv.io (HELO mail.localhost) (213.138.108.180) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 20:49:49 -0000 Received: by mail.localhost (Postfix, from userid 2001) id A87E24C18E; Fri, 17 Apr 2015 20:49:48 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on adm02.default.planetlarg.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.2 Received: from [10.0.1.28] (unknown [217.10.134.62]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localhost (Postfix) with ESMTPSA id AB1324C105 for ; Fri, 17 Apr 2015 20:49:47 +0000 (UTC) From: Nick Hardiman Message-Id: Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Date: Fri, 17 Apr 2015 21:49:47 +0100 References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> To: mirageos-devel@lists.xenproject.org In-Reply-To: X-Mailer: Apple Mail (2.2070.6) Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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="===============3950354575535310848==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3950354575535310848== Content-Type: multipart/alternative; boundary="Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78" --Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 What is the advantage of Scaleways, apart from the processor? What kind = of centralized hosting do you want?=20 I=E2=80=99m guessing two types -=20 1. image hosting * jitsu (no pressure, Magnus) * xen 2. dev hosting * ARMv7 * pre-built images Is that a decent infrastructure vision of the future?=20 What about -=20 * memory? * SSD space? What kind of public machine rental would be ideal? > On 17 Apr 2015, at 15:52, Anil Madhavapeddy wrote: >=20 >>=20 >> On 17 Apr 2015, at 15:50, Amir Chaudhry wrote: >>=20 >>=20 >> On 17 Apr 2015, at 12:00, Anil Madhavapeddy wrote: >>=20 >>> - In the meanwhile though, it works great for userspace builds of >>> Xen/ARM kernels, so it could be a good place to augment mirage-www's >>> deployment scripts to also build ARM images as well as x86. This >>> requires David Sheets' GitHub watcher which is making fast progress. >>> It might also be interesting to run a Jitsu daemon on them in >>> "userspace" with a Mirage tuntap Unix binary >>=20 >> Sounds like we could use Scaleway's cloud to automate build and = deployments to cubieboards (in a similar way to how we use Travis and = GitHub right now [1, 2]). Am I right? That would be really cool and = mitigate some of the issues around cross-compliation. >=20 > Yep, that's right. They build the same ARMv7 kernels as a Cubieboard = does today. >=20 > -anil >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org = > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = --Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
What is the advantage of Scaleways, apart = from the processor? What kind of centralized hosting do you = want? 

I=E2=80=99m guessing two types - 
1. image hosting
* = jitsu (no pressure, Magnus)
* xen

2. dev hosting
* ARMv7
* pre-built = images

Is that = a decent infrastructure vision of the future? 
What about - 
* memory?
* SSD space?

What kind of public machine rental would be ideal?



On 17 Apr 2015, at 15:52, Anil Madhavapeddy <anil@recoil.org> = wrote:


On 17 Apr 2015, = at 15:50, Amir Chaudhry <amc79@cam.ac.uk> wrote:

On 17 Apr 2015, at 12:00, Anil Madhavapeddy <anil@recoil.org> = wrote:

-= In the meanwhile though, it works great for userspace builds of
Xen/ARM kernels, so it could be a good place to augment = mirage-www's
deployment scripts to also build ARM images = as well as x86.  This
requires David Sheets' GitHub = watcher which is making fast progress.
It might also be = interesting to run a Jitsu daemon on them in
"userspace" = with a Mirage tuntap Unix binary

Sounds like we could use Scaleway's cloud to automate build = and deployments to cubieboards (in a similar way to how we use Travis = and GitHub right now [1, 2]).  Am I right?  That would be = really cool and mitigate some of the issues around cross-compliation.

Yep, that's right. =  They build the same ARMv7 kernels as a Cubieboard does = today.

-anil


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

= --Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78-- --===============3950354575535310848== 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 --===============3950354575535310848==-- From mirageos-devel-bounces@lists.xenproject.org Fri Apr 17 20:50:07 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Apr 2015 20:50:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjDD5-0005DB-79; Fri, 17 Apr 2015 20:49:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjDD3-0005D2-NJ for mirageos-devel@lists.xenproject.org; Fri, 17 Apr 2015 20:49:57 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id DB/E7-14975-4F171355; Fri, 17 Apr 2015 20:49:56 +0000 X-Env-Sender: nick@internetmachines.co.uk X-Msg-Ref: server-12.tower-31.messagelabs.com!1429303789!17536503!1 X-Originating-IP: [213.138.108.180] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31531 invoked from network); 17 Apr 2015 20:49:49 -0000 Received: from adm02.default.planetlarg.uk0.bigv.io (HELO mail.localhost) (213.138.108.180) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2015 20:49:49 -0000 Received: by mail.localhost (Postfix, from userid 2001) id A87E24C18E; Fri, 17 Apr 2015 20:49:48 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on adm02.default.planetlarg.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.2 Received: from [10.0.1.28] (unknown [217.10.134.62]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localhost (Postfix) with ESMTPSA id AB1324C105 for ; Fri, 17 Apr 2015 20:49:47 +0000 (UTC) From: Nick Hardiman Message-Id: Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Date: Fri, 17 Apr 2015 21:49:47 +0100 References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> To: mirageos-devel@lists.xenproject.org In-Reply-To: X-Mailer: Apple Mail (2.2070.6) Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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="===============3950354575535310848==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3950354575535310848== Content-Type: multipart/alternative; boundary="Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78" --Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 What is the advantage of Scaleways, apart from the processor? What kind = of centralized hosting do you want?=20 I=E2=80=99m guessing two types -=20 1. image hosting * jitsu (no pressure, Magnus) * xen 2. dev hosting * ARMv7 * pre-built images Is that a decent infrastructure vision of the future?=20 What about -=20 * memory? * SSD space? What kind of public machine rental would be ideal? > On 17 Apr 2015, at 15:52, Anil Madhavapeddy wrote: >=20 >>=20 >> On 17 Apr 2015, at 15:50, Amir Chaudhry wrote: >>=20 >>=20 >> On 17 Apr 2015, at 12:00, Anil Madhavapeddy wrote: >>=20 >>> - In the meanwhile though, it works great for userspace builds of >>> Xen/ARM kernels, so it could be a good place to augment mirage-www's >>> deployment scripts to also build ARM images as well as x86. This >>> requires David Sheets' GitHub watcher which is making fast progress. >>> It might also be interesting to run a Jitsu daemon on them in >>> "userspace" with a Mirage tuntap Unix binary >>=20 >> Sounds like we could use Scaleway's cloud to automate build and = deployments to cubieboards (in a similar way to how we use Travis and = GitHub right now [1, 2]). Am I right? That would be really cool and = mitigate some of the issues around cross-compliation. >=20 > Yep, that's right. They build the same ARMv7 kernels as a Cubieboard = does today. >=20 > -anil >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org = > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = --Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
What is the advantage of Scaleways, apart = from the processor? What kind of centralized hosting do you = want? 

I=E2=80=99m guessing two types - 
1. image hosting
* = jitsu (no pressure, Magnus)
* xen

2. dev hosting
* ARMv7
* pre-built = images

Is that = a decent infrastructure vision of the future? 
What about - 
* memory?
* SSD space?

What kind of public machine rental would be ideal?



On 17 Apr 2015, at 15:52, Anil Madhavapeddy <anil@recoil.org> = wrote:


On 17 Apr 2015, = at 15:50, Amir Chaudhry <amc79@cam.ac.uk> wrote:

On 17 Apr 2015, at 12:00, Anil Madhavapeddy <anil@recoil.org> = wrote:

-= In the meanwhile though, it works great for userspace builds of
Xen/ARM kernels, so it could be a good place to augment = mirage-www's
deployment scripts to also build ARM images = as well as x86.  This
requires David Sheets' GitHub = watcher which is making fast progress.
It might also be = interesting to run a Jitsu daemon on them in
"userspace" = with a Mirage tuntap Unix binary

Sounds like we could use Scaleway's cloud to automate build = and deployments to cubieboards (in a similar way to how we use Travis = and GitHub right now [1, 2]).  Am I right?  That would be = really cool and mitigate some of the issues around cross-compliation.

Yep, that's right. =  They build the same ARMv7 kernels as a Cubieboard does = today.

-anil


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

= --Apple-Mail=_1CB7C839-A8D6-4696-A12A-D3C4BDFA4D78-- --===============3950354575535310848== 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 --===============3950354575535310848==-- From mirageos-devel-bounces@lists.xenproject.org Sat Apr 18 08:48:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 08:48: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 1YjOQN-000614-SA; Sat, 18 Apr 2015 08:48:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjOQL-00060z-WA for mirageos-devel@lists.xenproject.org; Sat, 18 Apr 2015 08:48:26 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id A9/FE-23555-95A12355; Sat, 18 Apr 2015 08:48:25 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-4.tower-31.messagelabs.com!1429346903!17638671!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21022 invoked from network); 18 Apr 2015 08:48:24 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-4.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 08:48:24 -0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0FF0B20996 for ; Sat, 18 Apr 2015 04:48:23 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Sat, 18 Apr 2015 04:48:23 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=haJn6vPvYNo7GOhzfYaYdBpcfqc=; b=O3idR9 9AQiuloofTfFRwjke53W17mz5N5OKLyXf+HeWRXHw/qVwGG/gxXqvsdZZKrVDBBj neRhSiUsssO62IXOP/SH5L7uhbK2daW8L63wgG4fAMdf8WN0p9+0r+S9JLaWizcv vN3g1RyihOpa0TvP2sh0c7JG168DVrObraVEI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=haJn6vPvYNo7GOh zfYaYdBpcfqc=; b=XrofnzG4yUlg7whjmc/M4Y7BveOMl9VGNgmIb4YwxH8ZRLe xLktY2lXxQIwXT1lPbe0pREl5tiGlJViyccYS4ncC5Rttro2mrV/8iJvxEOtFGRh /vV/EfQ9fwxJNCInCMZnsr0MY0TJOUtjHLh5Q0LVjPMLSOt8kuoB4rzTSE+I= Received: by web1.nyi.internal (Postfix, from userid 99) id CB539AF3C80; Sat, 18 Apr 2015 04:48:22 -0400 (EDT) Message-Id: <1429346902.2502315.255375445.1B82BCEC@webmail.messagingengine.com> X-Sasl-Enc: F/6yMSzBR3dKLUMIfXOhxg0LrJmLylXJ4PFBIaLBTKqF 1429346902 From: Magnus Skjegstad To: Nick Hardiman , mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-424f40c2 Date: Sat, 18 Apr 2015 09:48:22 +0100 In-Reply-To: References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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="===============0738082428769362541==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============0738082428769362541== Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_142934690225023150"; charset="utf-8" This is a multi-part message in MIME format. --_----------=_142934690225023150 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" On Fri, 17 Apr 2015, at 21:49, Nick Hardiman wrote: > What is the advantage of Scaleways, apart from the processor? What > kind of centralized hosting do you want? > > I=E2=80=99m guessing two types - > > 1. image hosting > * jitsu (no pressure, Magnus) > * xen I'm looking for somewhere I can run Jitsu as a DNS server and be able to start unikernels on demand (with low latency). Whether it is ARM or x86 is not that important as Mirage and Jitsu works well on both platforms. It looks like Scaleway could be perfect for this if they add a kernel with Xen support. I could start unikernels as processes with Jitsu as well (as Anil suggested), but I wouldn't be able to isolate them in the same way as I would with Xen VMs. > 2. dev hosting > * ARMv7 > * pre-built images > > Is that a decent infrastructure vision of the future? What about - > * memory? > * SSD space? > > What kind of public machine rental would be ideal? For hosting services with Jitsu it would be great to be able to run one core instance that acted as a controller and then be able to quickly (<100ms) spin up smaller instances for unikernel VMs on demand. I would expect that the unikernel VMs in general would have low resource requirements (e.g 0-1GB storage, 16-64mb RAM), but could also require more resources in some cases (e.g. a db/file server with more memory/storage). I think a small ARM- or Intel NUC-based Xen server could work well for this. It could also be interesting to be able to boot small instances with higher latency to offload the main server. For example, an Amazon EC2 instance could be spun up (in minutes?) for a service that was experiencing high load/traffic and future DNS requests could be directed there by Jitsu (e.g. based on geographical region, etc). > >> On 17 Apr 2015, at 15:52, Anil Madhavapeddy wrote: >> >>> >>> On 17 Apr 2015, at 15:50, Amir Chaudhry wrote: >>> >>> >>> On 17 Apr 2015, at 12:00, Anil Madhavapeddy wrote: >>> >>>> - In the meanwhile though, it works great for userspace builds of >>>> Xen/ARM kernels, so it could be a good place to augment >>>> mirage-www's deployment scripts to also build ARM images as well >>>> as x86. This requires David Sheets' GitHub watcher which is >>>> making fast progress. It might also be interesting to run a Jitsu >>>> daemon on them in "userspace" with a Mirage tuntap Unix binary >>> >>> Sounds like we could use Scaleway's cloud to automate build and >>> deployments to cubieboards (in a similar way to how we use Travis >>> and GitHub right now [1, 2]). Am I right? That would be really cool >>> and mitigate some of the issues around cross-compliation. >> >> Yep, that's right. They build the same ARMv7 kernels as a Cubieboard >> does today. >> >> -anil >> >> >> _______________________________________________ >> 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 Magnus --_----------=_142934690225023150 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="UTF-8"
On Fri, 17 Apr 2015, at 21:49, Nick Hardiman wrote:
What is the advantage of Scaleway= s, apart from the processor? What kind of centralized hosting do you want?&= nbsp;
 
I=E2=80=99m guessing two types - 
 
1. image hosting
* jitsu (no pressure, Magnus)
* xen
 
I'm looking for somewhere I can run Jitsu as a DNS server and be able = to start unikernels on demand (with low latency). Whether it is ARM or x86 = is not that important as Mirage and Jitsu works well on both platforms. It = looks like Scaleway could be perfect for this if they add a kernel with Xen= support. I could start unikernels as processes with Jitsu as well (as Anil= suggested), but I wouldn't be able to isolate them in the same way as I wo= uld with Xen VMs.
 
2. dev hosting
* ARMv7
* pre-built images
 
Is that a decent infrastructure vision of the future? =
What about - 
* memory?
* SSD space?
 
What kind of public machine rental would be ideal?
 
For hosting services with Jitsu it would be great to be able to run on= e core instance that acted as a controller and then be able to quickly (<= ;100ms) spin up smaller instances for unikernel VMs on demand. I would expe= ct that the unikernel VMs in general would have low resource requirements = (e.g 0-1GB storage, 16-64mb RAM), but could also require more resources in = some cases (e.g. a db/file server with more memory/storage). I think a smal= l ARM- or Intel NUC-based Xen server could work well for this.
 
It could also be interesting to be able to boot small instances with h= igher latency to offload the main server. For example, an Amazon EC2 instan= ce could be spun up (in minutes?) for a service that was experiencing high = load/traffic and future DNS requests could be directed there by Jitsu (e.g.= based on geographical region, etc).
 
 
On 17 Apr 2015, a= t 15:52, Anil Madhavapeddy <anil@recoil.org> wrote:
 
 
On 17 Apr 2015, at 15:50, Amir Chaudhry <amc79@cam.ac.uk> wrote= :
 
 
On 17 Apr 2015, at 12:00, Anil Madhavapeddy <anil@recoil.org> w= rote:
 
- In the meanwhile though, it works gr= eat for userspace builds of
Xen/ARM kernels, so it could be a= good place to augment mirage-www's
deployment scripts to als= o build ARM images as well as x86.  This
requires David = Sheets' GitHub watcher which is making fast progress.
It migh= t also be interesting to run a Jitsu daemon on them in
"users= pace" with a Mirage tuntap Unix binary
 
Sounds like we could use Scaleway's cloud to automate build and deploy= ments to cubieboards (in a similar way to how we use Travis and GitHub righ= t now [1, 2]).  Am I right?  That would be really cool and mitiga= te some of the issues around cross-compliation.
 
Yep, that's right.  They build the same A= RMv7 kernels as a Cubieboard does today.
 
-anil
 
 
______________________________________________= _
 
_______________________________________________
MirageOS-devel mailing list
 
Magnus
--_----------=_142934690225023150-- --===============0738082428769362541== 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 --===============0738082428769362541==-- From mirageos-devel-bounces@lists.xenproject.org Sat Apr 18 08:48:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 08:48: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 1YjOQN-000614-SA; Sat, 18 Apr 2015 08:48:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjOQL-00060z-WA for mirageos-devel@lists.xenproject.org; Sat, 18 Apr 2015 08:48:26 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id A9/FE-23555-95A12355; Sat, 18 Apr 2015 08:48:25 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-4.tower-31.messagelabs.com!1429346903!17638671!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21022 invoked from network); 18 Apr 2015 08:48:24 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-4.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 08:48:24 -0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0FF0B20996 for ; Sat, 18 Apr 2015 04:48:23 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Sat, 18 Apr 2015 04:48:23 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=haJn6vPvYNo7GOhzfYaYdBpcfqc=; b=O3idR9 9AQiuloofTfFRwjke53W17mz5N5OKLyXf+HeWRXHw/qVwGG/gxXqvsdZZKrVDBBj neRhSiUsssO62IXOP/SH5L7uhbK2daW8L63wgG4fAMdf8WN0p9+0r+S9JLaWizcv vN3g1RyihOpa0TvP2sh0c7JG168DVrObraVEI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=haJn6vPvYNo7GOh zfYaYdBpcfqc=; b=XrofnzG4yUlg7whjmc/M4Y7BveOMl9VGNgmIb4YwxH8ZRLe xLktY2lXxQIwXT1lPbe0pREl5tiGlJViyccYS4ncC5Rttro2mrV/8iJvxEOtFGRh /vV/EfQ9fwxJNCInCMZnsr0MY0TJOUtjHLh5Q0LVjPMLSOt8kuoB4rzTSE+I= Received: by web1.nyi.internal (Postfix, from userid 99) id CB539AF3C80; Sat, 18 Apr 2015 04:48:22 -0400 (EDT) Message-Id: <1429346902.2502315.255375445.1B82BCEC@webmail.messagingengine.com> X-Sasl-Enc: F/6yMSzBR3dKLUMIfXOhxg0LrJmLylXJ4PFBIaLBTKqF 1429346902 From: Magnus Skjegstad To: Nick Hardiman , mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-424f40c2 Date: Sat, 18 Apr 2015 09:48:22 +0100 In-Reply-To: References: <1429267906.1455655.255026405.714DB875@webmail.messagingengine.com> <2E0B948C-9011-4184-86FB-5B6EDE3C9F4E@recoil.org> Subject: Re: [MirageOS-devel] Unikernel/Xen server hosting 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="===============0738082428769362541==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============0738082428769362541== Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_142934690225023150"; charset="utf-8" This is a multi-part message in MIME format. --_----------=_142934690225023150 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" On Fri, 17 Apr 2015, at 21:49, Nick Hardiman wrote: > What is the advantage of Scaleways, apart from the processor? What > kind of centralized hosting do you want? > > I=E2=80=99m guessing two types - > > 1. image hosting > * jitsu (no pressure, Magnus) > * xen I'm looking for somewhere I can run Jitsu as a DNS server and be able to start unikernels on demand (with low latency). Whether it is ARM or x86 is not that important as Mirage and Jitsu works well on both platforms. It looks like Scaleway could be perfect for this if they add a kernel with Xen support. I could start unikernels as processes with Jitsu as well (as Anil suggested), but I wouldn't be able to isolate them in the same way as I would with Xen VMs. > 2. dev hosting > * ARMv7 > * pre-built images > > Is that a decent infrastructure vision of the future? What about - > * memory? > * SSD space? > > What kind of public machine rental would be ideal? For hosting services with Jitsu it would be great to be able to run one core instance that acted as a controller and then be able to quickly (<100ms) spin up smaller instances for unikernel VMs on demand. I would expect that the unikernel VMs in general would have low resource requirements (e.g 0-1GB storage, 16-64mb RAM), but could also require more resources in some cases (e.g. a db/file server with more memory/storage). I think a small ARM- or Intel NUC-based Xen server could work well for this. It could also be interesting to be able to boot small instances with higher latency to offload the main server. For example, an Amazon EC2 instance could be spun up (in minutes?) for a service that was experiencing high load/traffic and future DNS requests could be directed there by Jitsu (e.g. based on geographical region, etc). > >> On 17 Apr 2015, at 15:52, Anil Madhavapeddy wrote: >> >>> >>> On 17 Apr 2015, at 15:50, Amir Chaudhry wrote: >>> >>> >>> On 17 Apr 2015, at 12:00, Anil Madhavapeddy wrote: >>> >>>> - In the meanwhile though, it works great for userspace builds of >>>> Xen/ARM kernels, so it could be a good place to augment >>>> mirage-www's deployment scripts to also build ARM images as well >>>> as x86. This requires David Sheets' GitHub watcher which is >>>> making fast progress. It might also be interesting to run a Jitsu >>>> daemon on them in "userspace" with a Mirage tuntap Unix binary >>> >>> Sounds like we could use Scaleway's cloud to automate build and >>> deployments to cubieboards (in a similar way to how we use Travis >>> and GitHub right now [1, 2]). Am I right? That would be really cool >>> and mitigate some of the issues around cross-compliation. >> >> Yep, that's right. They build the same ARMv7 kernels as a Cubieboard >> does today. >> >> -anil >> >> >> _______________________________________________ >> 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 Magnus --_----------=_142934690225023150 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="UTF-8"
On Fri, 17 Apr 2015, at 21:49, Nick Hardiman wrote:
What is the advantage of Scaleway= s, apart from the processor? What kind of centralized hosting do you want?&= nbsp;
 
I=E2=80=99m guessing two types - 
 
1. image hosting
* jitsu (no pressure, Magnus)
* xen
 
I'm looking for somewhere I can run Jitsu as a DNS server and be able = to start unikernels on demand (with low latency). Whether it is ARM or x86 = is not that important as Mirage and Jitsu works well on both platforms. It = looks like Scaleway could be perfect for this if they add a kernel with Xen= support. I could start unikernels as processes with Jitsu as well (as Anil= suggested), but I wouldn't be able to isolate them in the same way as I wo= uld with Xen VMs.
 
2. dev hosting
* ARMv7
* pre-built images
 
Is that a decent infrastructure vision of the future? =
What about - 
* memory?
* SSD space?
 
What kind of public machine rental would be ideal?
 
For hosting services with Jitsu it would be great to be able to run on= e core instance that acted as a controller and then be able to quickly (<= ;100ms) spin up smaller instances for unikernel VMs on demand. I would expe= ct that the unikernel VMs in general would have low resource requirements = (e.g 0-1GB storage, 16-64mb RAM), but could also require more resources in = some cases (e.g. a db/file server with more memory/storage). I think a smal= l ARM- or Intel NUC-based Xen server could work well for this.
 
It could also be interesting to be able to boot small instances with h= igher latency to offload the main server. For example, an Amazon EC2 instan= ce could be spun up (in minutes?) for a service that was experiencing high = load/traffic and future DNS requests could be directed there by Jitsu (e.g.= based on geographical region, etc).
 
 
On 17 Apr 2015, a= t 15:52, Anil Madhavapeddy <anil@recoil.org> wrote:
 
 
On 17 Apr 2015, at 15:50, Amir Chaudhry <amc79@cam.ac.uk> wrote= :
 
 
On 17 Apr 2015, at 12:00, Anil Madhavapeddy <anil@recoil.org> w= rote:
 
- In the meanwhile though, it works gr= eat for userspace builds of
Xen/ARM kernels, so it could be a= good place to augment mirage-www's
deployment scripts to als= o build ARM images as well as x86.  This
requires David = Sheets' GitHub watcher which is making fast progress.
It migh= t also be interesting to run a Jitsu daemon on them in
"users= pace" with a Mirage tuntap Unix binary
 
Sounds like we could use Scaleway's cloud to automate build and deploy= ments to cubieboards (in a similar way to how we use Travis and GitHub righ= t now [1, 2]).  Am I right?  That would be really cool and mitiga= te some of the issues around cross-compliation.
 
Yep, that's right.  They build the same A= RMv7 kernels as a Cubieboard does today.
 
-anil
 
 
______________________________________________= _
 
_______________________________________________
MirageOS-devel mailing list
 
Magnus
--_----------=_142934690225023150-- --===============0738082428769362541== 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 --===============0738082428769362541==-- From mirageos-devel-bounces@lists.xenproject.org Sat Apr 18 11:30:58 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 11:30: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 1YjQxW-0003jk-5r; Sat, 18 Apr 2015 11:30:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjQxU-0003jf-RG for mirageos-devel@lists.xenproject.org; Sat, 18 Apr 2015 11:30:48 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id A3/CD-09361-76042355; Sat, 18 Apr 2015 11:30:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1429356647!13274621!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32527 invoked from network); 18 Apr 2015 11:30:47 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 11:30:47 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id db4b3073; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 18 Apr 2015 12:30:45 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5530B39F.2050802@mehnert.org> Date: Sat, 18 Apr 2015 12:30:47 +0100 Message-Id: <73748AB8-5C6A-4146-8EE9-F89446212C43@recoil.org> References: <5530B39F.2050802@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] [ANN] release of Mirage 2.4.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 On 17 Apr 2015, at 08:17, Hannes Mehnert wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > On 04/17/2015 00:02, Thomas Gazagnaire wrote: >> I've just released mirage 2.4.0 in opam, which goes together with >> conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and >> mirage-http.2.2.0. These releases improve the TLS support, fix ARP >> issues, make the mirage HTTP server signature only depend on >> V1.FLOW and fix some usability issues with the mirage command-line >> tool. > > great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, > namely not dealing well with trailing bytes, as described by Magnus > Therning on this list. > > Also, the TLS/entropy story is not yet in its final shape (and will be > improved on, see David Kaloper's thread 'update on entropy', and some > discussion in https://github.com/mirage/mirage/pull/390). I've explicitly disabled Mirage/TLS in Conduit.0.8.2 to make sure it doesn't "escape" before it's ready. You need to pin and modify it to detect TLS for now, so we can prepare the release properly when David finishes the entropy support. -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 Apr 18 11:30:58 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 11:30: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 1YjQxW-0003jk-5r; Sat, 18 Apr 2015 11:30:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjQxU-0003jf-RG for mirageos-devel@lists.xenproject.org; Sat, 18 Apr 2015 11:30:48 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id A3/CD-09361-76042355; Sat, 18 Apr 2015 11:30:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1429356647!13274621!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32527 invoked from network); 18 Apr 2015 11:30:47 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 11:30:47 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id db4b3073; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 18 Apr 2015 12:30:45 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <5530B39F.2050802@mehnert.org> Date: Sat, 18 Apr 2015 12:30:47 +0100 Message-Id: <73748AB8-5C6A-4146-8EE9-F89446212C43@recoil.org> References: <5530B39F.2050802@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] [ANN] release of Mirage 2.4.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 On 17 Apr 2015, at 08:17, Hannes Mehnert wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > On 04/17/2015 00:02, Thomas Gazagnaire wrote: >> I've just released mirage 2.4.0 in opam, which goes together with >> conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and >> mirage-http.2.2.0. These releases improve the TLS support, fix ARP >> issues, make the mirage HTTP server signature only depend on >> V1.FLOW and fix some usability issues with the mirage command-line >> tool. > > great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, > namely not dealing well with trailing bytes, as described by Magnus > Therning on this list. > > Also, the TLS/entropy story is not yet in its final shape (and will be > improved on, see David Kaloper's thread 'update on entropy', and some > discussion in https://github.com/mirage/mirage/pull/390). I've explicitly disabled Mirage/TLS in Conduit.0.8.2 to make sure it doesn't "escape" before it's ready. You need to pin and modify it to detect TLS for now, so we can prepare the release properly when David finishes the entropy support. -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 Apr 18 15:32:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 15:32: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 1YjUj1-0005HW-4U; Sat, 18 Apr 2015 15:32:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUiz-0005HR-Uj for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 15:32:06 +0000 Received: from [85.158.139.211] by server-7.bemta-5.messagelabs.com id DF/EA-02028-5F872355; Sat, 18 Apr 2015 15:32:05 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1429371124!16875690!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP,WEIRD_QUOTING X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14036 invoked from network); 18 Apr 2015 15:32:04 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Apr 2015 15:32:04 -0000 Received: by wicmx19 with SMTP id mx19so9221971wic.1 for ; Sat, 18 Apr 2015 08:32:04 -0700 (PDT) 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=oZyU2BDDJv9tmwZVkDGKkCwLOA4pw1JavRQ2r9BtE5E=; b=D+IoRCjTGA1iyg/pIZll/SC2ghbPRB9U+Fdl8HopQ4Wi1TrevE1A12poly/6xPwI3h fi7T6EEjWr6YYbuXLQGhMVLSld1RQbyvAPdid70bw1dunIR+GCHXj9EWTDgCtYwyxgkL UgA1+7QhY6dDAfFBHo7KJ+KOa+0nOvWften4MpowU8UVkUrcPl7nnoWZ8KfdkmydsMow mnzuFFs3NHM53eO4vobbNLg1cT520zKzqaBfF0TaaKwp6QvVCf20YXlafGxuqsHgPmqV RbcoiDXpUu9cI1eGVzKR7s3cJSkR43vjjL2pCiEzJbqmMU/c0iXF04Li+Tw2ai0Y+Jcv eIkg== X-Received: by 10.194.203.74 with SMTP id ko10mr15161766wjc.96.1429371124154; Sat, 18 Apr 2015 08:32:04 -0700 (PDT) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com. [74.125.82.54]) by mx.google.com with ESMTPSA id n3sm19350748wja.36.2015.04.18.08.32.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Apr 2015 08:32:04 -0700 (PDT) Received: by wgin8 with SMTP id n8so139161414wgi.0 for ; Sat, 18 Apr 2015 08:32:03 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.98.97 with SMTP id eh1mr10544620wib.11.1429371123483; Sat, 18 Apr 2015 08:32:03 -0700 (PDT) Received: by 10.28.154.139 with HTTP; Sat, 18 Apr 2015 08:32:03 -0700 (PDT) Date: Sat, 18 Apr 2015 16:32:03 +0100 Message-ID: From: Richard Mortier To: mirageos-devel , opam-devel Subject: [MirageOS-devel] Problem with ocaml.janestreet.com TLS cert? 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 seem to be having a problem with the Jane Street TLS cert for ocaml.janestreet.com. OPAM is refusing to install sexplib etc as a result. I presume this is a curl TLS issue and I need a magic environment variable or something, but can't find it. Any ideas? This is on OSX using homebrew curl and OPAM 1.2.0. """ ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0curl: (56) SSLRead() return error -9841 000 [ERROR] https://ocaml.janestreet.com/ocaml-core/112.24/files/sexplib-112.24.01.tar.gz is not available [ERROR] Could not download archives of sexplib.112.24.01 'opam upgrade --verbose sexplib' failed. """" FWIW, visiting the site, Chrome complains: "The identity of this website has been verified by VeriSign Class 3 Secure Server CA - G3 but does not have public audit records. The site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it." and "Your connection to ocaml.janestreet.com is encrypted with obsolete cryptography. The connection uses TLS 1.2. The connection is encrypted and authenticated using AES_128_GCM and uses RSA as the key exchange mechanism." -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ 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 Apr 18 15:32:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 15:32: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 1YjUj1-0005HW-4U; Sat, 18 Apr 2015 15:32:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUiz-0005HR-Uj for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 15:32:06 +0000 Received: from [85.158.139.211] by server-7.bemta-5.messagelabs.com id DF/EA-02028-5F872355; Sat, 18 Apr 2015 15:32:05 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1429371124!16875690!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP,WEIRD_QUOTING X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14036 invoked from network); 18 Apr 2015 15:32:04 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Apr 2015 15:32:04 -0000 Received: by wicmx19 with SMTP id mx19so9221971wic.1 for ; Sat, 18 Apr 2015 08:32:04 -0700 (PDT) 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=oZyU2BDDJv9tmwZVkDGKkCwLOA4pw1JavRQ2r9BtE5E=; b=D+IoRCjTGA1iyg/pIZll/SC2ghbPRB9U+Fdl8HopQ4Wi1TrevE1A12poly/6xPwI3h fi7T6EEjWr6YYbuXLQGhMVLSld1RQbyvAPdid70bw1dunIR+GCHXj9EWTDgCtYwyxgkL UgA1+7QhY6dDAfFBHo7KJ+KOa+0nOvWften4MpowU8UVkUrcPl7nnoWZ8KfdkmydsMow mnzuFFs3NHM53eO4vobbNLg1cT520zKzqaBfF0TaaKwp6QvVCf20YXlafGxuqsHgPmqV RbcoiDXpUu9cI1eGVzKR7s3cJSkR43vjjL2pCiEzJbqmMU/c0iXF04Li+Tw2ai0Y+Jcv eIkg== X-Received: by 10.194.203.74 with SMTP id ko10mr15161766wjc.96.1429371124154; Sat, 18 Apr 2015 08:32:04 -0700 (PDT) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com. [74.125.82.54]) by mx.google.com with ESMTPSA id n3sm19350748wja.36.2015.04.18.08.32.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Apr 2015 08:32:04 -0700 (PDT) Received: by wgin8 with SMTP id n8so139161414wgi.0 for ; Sat, 18 Apr 2015 08:32:03 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.98.97 with SMTP id eh1mr10544620wib.11.1429371123483; Sat, 18 Apr 2015 08:32:03 -0700 (PDT) Received: by 10.28.154.139 with HTTP; Sat, 18 Apr 2015 08:32:03 -0700 (PDT) Date: Sat, 18 Apr 2015 16:32:03 +0100 Message-ID: From: Richard Mortier To: mirageos-devel , opam-devel Subject: [MirageOS-devel] Problem with ocaml.janestreet.com TLS cert? 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 seem to be having a problem with the Jane Street TLS cert for ocaml.janestreet.com. OPAM is refusing to install sexplib etc as a result. I presume this is a curl TLS issue and I need a magic environment variable or something, but can't find it. Any ideas? This is on OSX using homebrew curl and OPAM 1.2.0. """ ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0curl: (56) SSLRead() return error -9841 000 [ERROR] https://ocaml.janestreet.com/ocaml-core/112.24/files/sexplib-112.24.01.tar.gz is not available [ERROR] Could not download archives of sexplib.112.24.01 'opam upgrade --verbose sexplib' failed. """" FWIW, visiting the site, Chrome complains: "The identity of this website has been verified by VeriSign Class 3 Secure Server CA - G3 but does not have public audit records. The site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it." and "Your connection to ocaml.janestreet.com is encrypted with obsolete cryptography. The connection uses TLS 1.2. The connection is encrypted and authenticated using AES_128_GCM and uses RSA as the key exchange mechanism." -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ 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 Apr 18 15:35:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 15:35:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUm2-0005YM-Dp; Sat, 18 Apr 2015 15:35:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUm1-0005YH-Ni for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 15:35:13 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id B8/02-30672-0B972355; Sat, 18 Apr 2015 15:35:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1429371311!16880207!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP, WEIRD_QUOTING X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5915 invoked from network); 18 Apr 2015 15:35:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 15:35:12 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 2e8bc3a2; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 18 Apr 2015 16:35:11 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 18 Apr 2015 16:35:14 +0100 Message-Id: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> References: To: Richard Mortier , Yaron Minsky , Jeremie Dimino X-Mailer: Apple Mail (2.2098) Cc: opam-devel , mirageos-devel Subject: Re: [MirageOS-devel] [opam-devel] Problem with ocaml.janestreet.com TLS cert? 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 broken `curl` command on base OSX. Try switching to wget with: export OPAMFETCH=wget CCing Yaron Minsky and Jeremie Diminio about the Jane Street setup -- this is likely a result of disabling SSLv3 due to the POODLE attack. -anil > On 18 Apr 2015, at 16:32, Richard Mortier wrote: > > Hi; > > I seem to be having a problem with the Jane Street TLS cert for > ocaml.janestreet.com. OPAM is refusing to install sexplib etc as a > result. I presume this is a curl TLS issue and I need a magic > environment variable or something, but can't find it. Any ideas? > > This is on OSX using homebrew curl and OPAM 1.2.0. > > """ > ... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 > --:--:-- 0curl: (56) SSLRead() return error -9841 > 000 > [ERROR] https://ocaml.janestreet.com/ocaml-core/112.24/files/sexplib-112.24.01.tar.gz > is not available > [ERROR] Could not download archives of sexplib.112.24.01 > > 'opam upgrade --verbose sexplib' failed. > """" > > FWIW, visiting the site, Chrome complains: > > "The identity of this website has been verified by VeriSign Class 3 > Secure Server CA - G3 but does not have public audit records. > > The site is using outdated security settings that may prevent future > versions of Chrome from being able to safely access it." > > and > > "Your connection to ocaml.janestreet.com is encrypted with obsolete > cryptography. > > The connection uses TLS 1.2. > > The connection is encrypted and authenticated using AES_128_GCM and > uses RSA as the key exchange mechanism." > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-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 Sat Apr 18 15:35:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 15:35:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUm2-0005YM-Dp; Sat, 18 Apr 2015 15:35:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUm1-0005YH-Ni for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 15:35:13 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id B8/02-30672-0B972355; Sat, 18 Apr 2015 15:35:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1429371311!16880207!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP, WEIRD_QUOTING X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5915 invoked from network); 18 Apr 2015 15:35:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 15:35:12 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 2e8bc3a2; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 18 Apr 2015 16:35:11 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 18 Apr 2015 16:35:14 +0100 Message-Id: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> References: To: Richard Mortier , Yaron Minsky , Jeremie Dimino X-Mailer: Apple Mail (2.2098) Cc: opam-devel , mirageos-devel Subject: Re: [MirageOS-devel] [opam-devel] Problem with ocaml.janestreet.com TLS cert? 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 broken `curl` command on base OSX. Try switching to wget with: export OPAMFETCH=wget CCing Yaron Minsky and Jeremie Diminio about the Jane Street setup -- this is likely a result of disabling SSLv3 due to the POODLE attack. -anil > On 18 Apr 2015, at 16:32, Richard Mortier wrote: > > Hi; > > I seem to be having a problem with the Jane Street TLS cert for > ocaml.janestreet.com. OPAM is refusing to install sexplib etc as a > result. I presume this is a curl TLS issue and I need a magic > environment variable or something, but can't find it. Any ideas? > > This is on OSX using homebrew curl and OPAM 1.2.0. > > """ > ... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 > --:--:-- 0curl: (56) SSLRead() return error -9841 > 000 > [ERROR] https://ocaml.janestreet.com/ocaml-core/112.24/files/sexplib-112.24.01.tar.gz > is not available > [ERROR] Could not download archives of sexplib.112.24.01 > > 'opam upgrade --verbose sexplib' failed. > """" > > FWIW, visiting the site, Chrome complains: > > "The identity of this website has been verified by VeriSign Class 3 > Secure Server CA - G3 but does not have public audit records. > > The site is using outdated security settings that may prevent future > versions of Chrome from being able to safely access it." > > and > > "Your connection to ocaml.janestreet.com is encrypted with obsolete > cryptography. > > The connection uses TLS 1.2. > > The connection is encrypted and authenticated using AES_128_GCM and > uses RSA as the key exchange mechanism." > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-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 Sat Apr 18 15:35:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 15:35: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 1YjUmX-0005aH-Hc; Sat, 18 Apr 2015 15:35:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUmW-0005a9-1r for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 15:35:44 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id CC/2C-17455-FC972355; Sat, 18 Apr 2015 15:35:43 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-12.tower-31.messagelabs.com!1429371342!17648884!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19919 invoked from network); 18 Apr 2015 15:35:42 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-12.tower-31.messagelabs.com with SMTP; 18 Apr 2015 15:35:42 -0000 Received: from [172.20.10.2] (121.232.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch [178.197.232.121]) by smtp.webfaction.com (Postfix) with ESMTP id 00B45207903C; Sat, 18 Apr 2015 15:35:40 +0000 (UTC) Date: Sat, 18 Apr 2015 17:35:37 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Richard Mortier Message-ID: In-Reply-To: References: X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: opam-devel , mirageos-devel Subject: Re: [MirageOS-devel] Problem with ocaml.janestreet.com TLS cert? 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 Looks like this https://github.com/ocaml/opam/issues/2006 Daniel _______________________________________________ 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 Apr 18 15:35:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 15:35: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 1YjUmX-0005aH-Hc; Sat, 18 Apr 2015 15:35:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjUmW-0005a9-1r for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 15:35:44 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id CC/2C-17455-FC972355; Sat, 18 Apr 2015 15:35:43 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-12.tower-31.messagelabs.com!1429371342!17648884!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19919 invoked from network); 18 Apr 2015 15:35:42 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-12.tower-31.messagelabs.com with SMTP; 18 Apr 2015 15:35:42 -0000 Received: from [172.20.10.2] (121.232.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch [178.197.232.121]) by smtp.webfaction.com (Postfix) with ESMTP id 00B45207903C; Sat, 18 Apr 2015 15:35:40 +0000 (UTC) Date: Sat, 18 Apr 2015 17:35:37 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Richard Mortier Message-ID: In-Reply-To: References: X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: opam-devel , mirageos-devel Subject: Re: [MirageOS-devel] Problem with ocaml.janestreet.com TLS cert? 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 Looks like this https://github.com/ocaml/opam/issues/2006 Daniel _______________________________________________ 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 Apr 18 19:27:01 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 19:27: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 1YjYOD-0002jx-N2; Sat, 18 Apr 2015 19:26:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjYOC-0002js-IT for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 19:26:52 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 2A/9C-30165-BFFA2355; Sat, 18 Apr 2015 19:26:51 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1429385211!17721673!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30901 invoked from network); 18 Apr 2015 19:26:51 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Apr 2015 19:26:51 -0000 Received: by wgyo15 with SMTP id o15so142583643wgy.2 for ; Sat, 18 Apr 2015 12:26:51 -0700 (PDT) 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=cclEfjfIeypM97J+HulCf0n6AI5FY4zjXdc8lAaIfbQ=; b=dPleUJc+GWmBUP+rMOHebkScQ03s9kJZZMxiwQ3NYv0PTJTrfsBwu33meCIqB8wc5M GWSOS6no1HgjHfuIXE7Iy5Ubrdw/KdSthaS3fdnIpuBPTy+Ci1XKVKrggS8eKnO/RdoM 0PR+vwnKYos5a+4KsYZPZs1gora7YUoH3A12qnQ9MagFHXDRT2UxvMQ8olJHEVFSlmO3 Vsg81HTLe3WLQ9jljgrLxxdnMhOvKyt8YQGh5c5RTGIEM53CGgIqgq7bPEecDLaa5nvq ylfxkWpI4mN3AObeWyu0aMptvK9KbeyXj7qIAWhEpIAg7qHr8dX78llayXAN8zlVNBDP YNpg== X-Received: by 10.194.171.136 with SMTP id au8mr17249423wjc.6.1429385210893; Sat, 18 Apr 2015 12:26:50 -0700 (PDT) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com. [209.85.212.175]) by mx.google.com with ESMTPSA id uo6sm20086335wjc.49.2015.04.18.12.26.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Apr 2015 12:26:50 -0700 (PDT) Received: by widdi4 with SMTP id di4so56397891wid.0 for ; Sat, 18 Apr 2015 12:26:49 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.219.42 with SMTP id pl10mr11985438wic.70.1429385209882; Sat, 18 Apr 2015 12:26:49 -0700 (PDT) Received: by 10.28.154.139 with HTTP; Sat, 18 Apr 2015 12:26:49 -0700 (PDT) In-Reply-To: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> References: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> Date: Sat, 18 Apr 2015 20:26:49 +0100 Message-ID: From: Richard Mortier To: Anil Madhavapeddy Cc: Yaron Minsky , Jeremie Dimino , mirageos-devel , opam-devel Subject: Re: [MirageOS-devel] [opam-devel] Problem with ocaml.janestreet.com TLS cert? 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 April 2015 at 16:35, Anil Madhavapeddy wrote: > This is a broken `curl` command on base OSX. Try switching to wget with: > > export OPAMFETCH=wget Doesn't seem to be honoured by `opam upgrade`. Have filed an issue. -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ 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 Apr 18 19:27:01 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 19:27: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 1YjYOD-0002jx-N2; Sat, 18 Apr 2015 19:26:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjYOC-0002js-IT for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 19:26:52 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 2A/9C-30165-BFFA2355; Sat, 18 Apr 2015 19:26:51 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1429385211!17721673!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30901 invoked from network); 18 Apr 2015 19:26:51 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Apr 2015 19:26:51 -0000 Received: by wgyo15 with SMTP id o15so142583643wgy.2 for ; Sat, 18 Apr 2015 12:26:51 -0700 (PDT) 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=cclEfjfIeypM97J+HulCf0n6AI5FY4zjXdc8lAaIfbQ=; b=dPleUJc+GWmBUP+rMOHebkScQ03s9kJZZMxiwQ3NYv0PTJTrfsBwu33meCIqB8wc5M GWSOS6no1HgjHfuIXE7Iy5Ubrdw/KdSthaS3fdnIpuBPTy+Ci1XKVKrggS8eKnO/RdoM 0PR+vwnKYos5a+4KsYZPZs1gora7YUoH3A12qnQ9MagFHXDRT2UxvMQ8olJHEVFSlmO3 Vsg81HTLe3WLQ9jljgrLxxdnMhOvKyt8YQGh5c5RTGIEM53CGgIqgq7bPEecDLaa5nvq ylfxkWpI4mN3AObeWyu0aMptvK9KbeyXj7qIAWhEpIAg7qHr8dX78llayXAN8zlVNBDP YNpg== X-Received: by 10.194.171.136 with SMTP id au8mr17249423wjc.6.1429385210893; Sat, 18 Apr 2015 12:26:50 -0700 (PDT) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com. [209.85.212.175]) by mx.google.com with ESMTPSA id uo6sm20086335wjc.49.2015.04.18.12.26.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Apr 2015 12:26:50 -0700 (PDT) Received: by widdi4 with SMTP id di4so56397891wid.0 for ; Sat, 18 Apr 2015 12:26:49 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.219.42 with SMTP id pl10mr11985438wic.70.1429385209882; Sat, 18 Apr 2015 12:26:49 -0700 (PDT) Received: by 10.28.154.139 with HTTP; Sat, 18 Apr 2015 12:26:49 -0700 (PDT) In-Reply-To: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> References: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> Date: Sat, 18 Apr 2015 20:26:49 +0100 Message-ID: From: Richard Mortier To: Anil Madhavapeddy Cc: Yaron Minsky , Jeremie Dimino , mirageos-devel , opam-devel Subject: Re: [MirageOS-devel] [opam-devel] Problem with ocaml.janestreet.com TLS cert? 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 April 2015 at 16:35, Anil Madhavapeddy wrote: > This is a broken `curl` command on base OSX. Try switching to wget with: > > export OPAMFETCH=wget Doesn't seem to be honoured by `opam upgrade`. Have filed an issue. -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ 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 Apr 18 22:15:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 22:15:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yjb1V-0003R2-5W; Sat, 18 Apr 2015 22:15:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjXtC-00015l-SN for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 18:54:51 +0000 Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id 57/E8-24632-A78A2355; Sat, 18 Apr 2015 18:54:50 +0000 X-Env-Sender: edwin+ml-ocaml@etorok.net X-Msg-Ref: server-11.tower-31.messagelabs.com!1429383288!17781365!1 X-Originating-IP: [62.113.205.31] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17715 invoked from network); 18 Apr 2015 18:54:49 -0000 Received: from mx.etorok.net (HELO mx.etorok.net) (62.113.205.31) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 18:54:49 -0000 Received: by mx.etorok.net (OpenSMTPD) with ESMTP id fade48c2; Sat, 18 Apr 2015 21:54:47 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=etorok.net; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=ml; bh=rG ZUbpXAOoTFWJEk2otVGdzTbrA=; b=nQScEAgZSCIZEul2op1ufo/nuwfaScizyl 59wIE1u0m+drPGmk1M37pgr7aEKmKaaYHNERTm+wHPnU7NOnAeYY0tbiDZ3g6kk2 K6s6/k1DGWPeHErfV9SERYQ1ZdXSrD6gUEngaS9e2Ra0eqHWRDqGkumgE5KmqqAa EIJseYw2g= Received: by mx.etorok.net (OpenSMTPD) with ESMTPSA id 2c9c43a6; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sat, 18 Apr 2015 21:54:40 +0300 (EEST) Message-ID: <5532A86E.60907@etorok.net> Date: Sat, 18 Apr 2015 21:54:38 +0300 From: =?windows-1252?Q?T=F6r=F6k_Edwin?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Anil Madhavapeddy , Richard Mortier , Yaron Minsky , Jeremie Dimino References: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> In-Reply-To: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> X-Mailman-Approved-At: Sat, 18 Apr 2015 22:15:35 +0000 Cc: opam-devel , mirageos-devel Subject: Re: [MirageOS-devel] [opam-devel] Problem with ocaml.janestreet.com TLS cert? 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 04/18/2015 06:35 PM, Anil Madhavapeddy wrote: > This is a broken `curl` command on base OSX. Try switching to wget with: > > export OPAMFETCH=wget > > CCing Yaron Minsky and Jeremie Diminio about the Jane Street setup -- this is > likely a result of disabling SSLv3 due to the POODLE attack. > >> FWIW, visiting the site, Chrome complains: I don't think this is related to the problem you're seeing with curl as curl works fine on Debian Jessie. >> >> "The identity of this website has been verified by VeriSign Class 3 >> Secure Server CA - G3 but does not have public audit records. >> >> The site is using outdated security settings that may prevent future >> versions of Chrome from being able to safely access it." https://community.qualys.com/blogs/securitylabs/2014/09/09/sha1-deprecation-what-you-need-to-know >> >> and >> >> "Your connection to ocaml.janestreet.com is encrypted with obsolete >> cryptography. >> >> The connection uses TLS 1.2. >> >> The connection is encrypted and authenticated using AES_128_GCM and >> uses RSA as the key exchange mechanism." >> Probably complains about lack of ECDHE, but then Firefox does use ECHDE, and Chrome doesn't: https://www.ssllabs.com/ssltest/analyze.html?d=ocaml.janestreet.com Best regards, --Edwin _______________________________________________ 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 Apr 18 22:15:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Apr 2015 22:15:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yjb1V-0003R2-5W; Sat, 18 Apr 2015 22:15:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjXtC-00015l-SN for MirageOS-devel@lists.xenproject.org; Sat, 18 Apr 2015 18:54:51 +0000 Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id 57/E8-24632-A78A2355; Sat, 18 Apr 2015 18:54:50 +0000 X-Env-Sender: edwin+ml-ocaml@etorok.net X-Msg-Ref: server-11.tower-31.messagelabs.com!1429383288!17781365!1 X-Originating-IP: [62.113.205.31] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17715 invoked from network); 18 Apr 2015 18:54:49 -0000 Received: from mx.etorok.net (HELO mx.etorok.net) (62.113.205.31) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2015 18:54:49 -0000 Received: by mx.etorok.net (OpenSMTPD) with ESMTP id fade48c2; Sat, 18 Apr 2015 21:54:47 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=etorok.net; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=ml; bh=rG ZUbpXAOoTFWJEk2otVGdzTbrA=; b=nQScEAgZSCIZEul2op1ufo/nuwfaScizyl 59wIE1u0m+drPGmk1M37pgr7aEKmKaaYHNERTm+wHPnU7NOnAeYY0tbiDZ3g6kk2 K6s6/k1DGWPeHErfV9SERYQ1ZdXSrD6gUEngaS9e2Ra0eqHWRDqGkumgE5KmqqAa EIJseYw2g= Received: by mx.etorok.net (OpenSMTPD) with ESMTPSA id 2c9c43a6; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sat, 18 Apr 2015 21:54:40 +0300 (EEST) Message-ID: <5532A86E.60907@etorok.net> Date: Sat, 18 Apr 2015 21:54:38 +0300 From: =?windows-1252?Q?T=F6r=F6k_Edwin?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Anil Madhavapeddy , Richard Mortier , Yaron Minsky , Jeremie Dimino References: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> In-Reply-To: <0B142F93-301C-44F4-A267-A8B77D46D6DB@recoil.org> X-Mailman-Approved-At: Sat, 18 Apr 2015 22:15:35 +0000 Cc: opam-devel , mirageos-devel Subject: Re: [MirageOS-devel] [opam-devel] Problem with ocaml.janestreet.com TLS cert? 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 04/18/2015 06:35 PM, Anil Madhavapeddy wrote: > This is a broken `curl` command on base OSX. Try switching to wget with: > > export OPAMFETCH=wget > > CCing Yaron Minsky and Jeremie Diminio about the Jane Street setup -- this is > likely a result of disabling SSLv3 due to the POODLE attack. > >> FWIW, visiting the site, Chrome complains: I don't think this is related to the problem you're seeing with curl as curl works fine on Debian Jessie. >> >> "The identity of this website has been verified by VeriSign Class 3 >> Secure Server CA - G3 but does not have public audit records. >> >> The site is using outdated security settings that may prevent future >> versions of Chrome from being able to safely access it." https://community.qualys.com/blogs/securitylabs/2014/09/09/sha1-deprecation-what-you-need-to-know >> >> and >> >> "Your connection to ocaml.janestreet.com is encrypted with obsolete >> cryptography. >> >> The connection uses TLS 1.2. >> >> The connection is encrypted and authenticated using AES_128_GCM and >> uses RSA as the key exchange mechanism." >> Probably complains about lack of ECDHE, but then Firefox does use ECHDE, and Chrome doesn't: https://www.ssllabs.com/ssltest/analyze.html?d=ocaml.janestreet.com Best regards, --Edwin _______________________________________________ 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 Apr 19 13:58:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 13:58: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 1YjpjQ-00071N-V6; Sun, 19 Apr 2015 13:57:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjpjP-00071I-SQ for MirageOS-devel@lists.xenproject.org; Sun, 19 Apr 2015 13:57:55 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 9A/F4-27592-364B3355; Sun, 19 Apr 2015 13:57:55 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1429451872!14469129!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7511 invoked from network); 19 Apr 2015 13:57:52 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2015 13:57:52 -0000 Received: by wgin8 with SMTP id n8so154229154wgi.0 for ; Sun, 19 Apr 2015 06:57:52 -0700 (PDT) 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=rgQOPrBG7JptOt1FXLx336rXGJ+VYYdrAOtcL5qzLaQ=; b=bskNru68zJTNb8Od9MZo0NGsq6I46s5fy04Wdr19ncvFLZP3BcPb4qYhlOkyFwefQY 78volIr57O/qdBZh+i8WpUG3aEjd6XLU3VHjoqK9SVAOCNff6N7v+VPPsheBsIBJFzMs tnhJH8DtUxjdOCzYFgxMgrC9OUjmLa7RfUwbzxOSe8FpyuZXOF2DbIanUlN7tEMKbwfc LIAyvLQQROr+iV7SX4Mjkp4ltQdDMOqQagCfc86ewKbrRLmCY5OHtAVhlHfFbiIUri0L lBv30CYCoRFAPWhZQ4g+O3GmzwGMOZvil7G8p0/zzYxGmB/PPe2yfJW/PalxBnt5VC7t D63w== X-Received: by 10.194.157.194 with SMTP id wo2mr4546795wjb.103.1429451872295; Sun, 19 Apr 2015 06:57:52 -0700 (PDT) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com. [209.85.212.177]) by mx.google.com with ESMTPSA id dg8sm23147083wjc.9.2015.04.19.06.57.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Apr 2015 06:57:52 -0700 (PDT) Received: by wiax7 with SMTP id x7so64840328wia.0 for ; Sun, 19 Apr 2015 06:57:51 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.60.173 with SMTP id i13mr22329371wjr.124.1429451871398; Sun, 19 Apr 2015 06:57:51 -0700 (PDT) Received: by 10.28.154.139 with HTTP; Sun, 19 Apr 2015 06:57:51 -0700 (PDT) Date: Sun, 19 Apr 2015 14:57:51 +0100 Message-ID: From: Richard Mortier To: mirageos-devel Subject: [MirageOS-devel] Vagrant VM images 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 All; I finally finished off tidying up the Vagrant VMs repo, http://github.com/mirage/mirage-vagrant-vms/. It should now support generation via the Makefile of valid Virtualbox images, from scratch, for use with Vagrant, for any of Ubuntu 14.{04,10}, Debian 7.8.0 and XenServer 6.5.0. The images are provisioned to the point that they have OCaml, OPAM and Mirage installed. Comments or pull requests (eg., networking probably still isn't optimally configured) welcome. Hope someone finds them useful! -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ 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 Apr 19 13:58:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 13:58: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 1YjpjQ-00071N-V6; Sun, 19 Apr 2015 13:57:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjpjP-00071I-SQ for MirageOS-devel@lists.xenproject.org; Sun, 19 Apr 2015 13:57:55 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 9A/F4-27592-364B3355; Sun, 19 Apr 2015 13:57:55 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1429451872!14469129!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7511 invoked from network); 19 Apr 2015 13:57:52 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2015 13:57:52 -0000 Received: by wgin8 with SMTP id n8so154229154wgi.0 for ; Sun, 19 Apr 2015 06:57:52 -0700 (PDT) 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=rgQOPrBG7JptOt1FXLx336rXGJ+VYYdrAOtcL5qzLaQ=; b=bskNru68zJTNb8Od9MZo0NGsq6I46s5fy04Wdr19ncvFLZP3BcPb4qYhlOkyFwefQY 78volIr57O/qdBZh+i8WpUG3aEjd6XLU3VHjoqK9SVAOCNff6N7v+VPPsheBsIBJFzMs tnhJH8DtUxjdOCzYFgxMgrC9OUjmLa7RfUwbzxOSe8FpyuZXOF2DbIanUlN7tEMKbwfc LIAyvLQQROr+iV7SX4Mjkp4ltQdDMOqQagCfc86ewKbrRLmCY5OHtAVhlHfFbiIUri0L lBv30CYCoRFAPWhZQ4g+O3GmzwGMOZvil7G8p0/zzYxGmB/PPe2yfJW/PalxBnt5VC7t D63w== X-Received: by 10.194.157.194 with SMTP id wo2mr4546795wjb.103.1429451872295; Sun, 19 Apr 2015 06:57:52 -0700 (PDT) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com. [209.85.212.177]) by mx.google.com with ESMTPSA id dg8sm23147083wjc.9.2015.04.19.06.57.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Apr 2015 06:57:52 -0700 (PDT) Received: by wiax7 with SMTP id x7so64840328wia.0 for ; Sun, 19 Apr 2015 06:57:51 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.60.173 with SMTP id i13mr22329371wjr.124.1429451871398; Sun, 19 Apr 2015 06:57:51 -0700 (PDT) Received: by 10.28.154.139 with HTTP; Sun, 19 Apr 2015 06:57:51 -0700 (PDT) Date: Sun, 19 Apr 2015 14:57:51 +0100 Message-ID: From: Richard Mortier To: mirageos-devel Subject: [MirageOS-devel] Vagrant VM images 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 All; I finally finished off tidying up the Vagrant VMs repo, http://github.com/mirage/mirage-vagrant-vms/. It should now support generation via the Makefile of valid Virtualbox images, from scratch, for use with Vagrant, for any of Ubuntu 14.{04,10}, Debian 7.8.0 and XenServer 6.5.0. The images are provisioned to the point that they have OCaml, OPAM and Mirage installed. Comments or pull requests (eg., networking probably still isn't optimally configured) welcome. Hope someone finds them useful! -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ 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 Apr 19 17:36:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 17:36:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yjt8U-0000zX-JG; Sun, 19 Apr 2015 17:36:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yjt8S-0000zS-Tz for mirageos-devel@lists.xenproject.org; Sun, 19 Apr 2015 17:36:01 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id 28/0F-07318-087E3355; Sun, 19 Apr 2015 17:36:00 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1429464956!17892253!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23539 invoked from network); 19 Apr 2015 17:35:57 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Apr 2015 17:35:57 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 727cb884; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 19 Apr 2015 18:35:55 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> Date: Sun, 19 Apr 2015 18:35:54 +0100 Message-Id: <4428E58D-BE52-4F91-B544-86BA2DFEAF81@recoil.org> References: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> To: Christophe Troestler X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Generic use of cohttp 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 Christophe, (+cc mirageos-devel) I was just talking to David Sheets about this last week, as he suggested that do put together a simple client based purely off the IO module in Cohttp. Right now you need to duplicate code across Async and Lwt backends for Cohttp, but I think that a HTTP_CLIENT module type that provides high-level get/put/patch/delete functions should be fairly straightforward over the newer Cohttps. Are you still working on the Dropbox bindings? thanks Anil > On 28 Dec 2014, at 23:55, Christophe Troestler wrote: > > Hi Anil, > > I'd like to build a library on top of cohttp that communicates with a > REST API using the Client module with an SSL endpoint. I'd like to > make this library generic so it can be used with all targets of > Conduit/Cohttp (Lwt & Async). Do I have to duplicate the code (in > addition to monadic operations, I will also need streams/pipes > because I must transfer files)? Suggestions are very welcome. > > Cheers, > C. > _______________________________________________ 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 Apr 19 17:36:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 17:36:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yjt8U-0000zX-JG; Sun, 19 Apr 2015 17:36:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yjt8S-0000zS-Tz for mirageos-devel@lists.xenproject.org; Sun, 19 Apr 2015 17:36:01 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id 28/0F-07318-087E3355; Sun, 19 Apr 2015 17:36:00 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1429464956!17892253!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23539 invoked from network); 19 Apr 2015 17:35:57 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Apr 2015 17:35:57 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 727cb884; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 19 Apr 2015 18:35:55 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> Date: Sun, 19 Apr 2015 18:35:54 +0100 Message-Id: <4428E58D-BE52-4F91-B544-86BA2DFEAF81@recoil.org> References: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> To: Christophe Troestler X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Generic use of cohttp 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 Christophe, (+cc mirageos-devel) I was just talking to David Sheets about this last week, as he suggested that do put together a simple client based purely off the IO module in Cohttp. Right now you need to duplicate code across Async and Lwt backends for Cohttp, but I think that a HTTP_CLIENT module type that provides high-level get/put/patch/delete functions should be fairly straightforward over the newer Cohttps. Are you still working on the Dropbox bindings? thanks Anil > On 28 Dec 2014, at 23:55, Christophe Troestler wrote: > > Hi Anil, > > I'd like to build a library on top of cohttp that communicates with a > REST API using the Client module with an SSL endpoint. I'd like to > make this library generic so it can be used with all targets of > Conduit/Cohttp (Lwt & Async). Do I have to duplicate the code (in > addition to monadic operations, I will also need streams/pipes > because I must transfer files)? Suggestions are very welcome. > > Cheers, > C. > _______________________________________________ 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 Apr 19 17:41:24 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 17:41: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 1YjtDg-0001TJ-7o; Sun, 19 Apr 2015 17:41:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjtDe-0001TE-GO for mirageos-devel@lists.xenproject.org; Sun, 19 Apr 2015 17:41:22 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id E0/B2-04861-1C8E3355; Sun, 19 Apr 2015 17:41:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1429465280!17877171!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22739 invoked from network); 19 Apr 2015 17:41:20 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Apr 2015 17:41:20 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 94660f36; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 19 Apr 2015 18:41:20 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <20150103.174914.2189911392197753803.Christophe.Troestler@umons.ac.be> Date: Sun, 19 Apr 2015 18:41:18 +0100 Message-Id: <9D65A5B6-CB97-46FF-A44F-5B108945094C@recoil.org> References: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> <20150103.174914.2189911392197753803.Christophe.Troestler@umons.ac.be> To: Christophe Troestler X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Generic use of cohttp 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="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMyBKYW4gMjAxNSwgYXQgMTY6NDksIENocmlzdG9waGUgVHJvZXN0bGVyIDxDaHJpc3RvcGhl LlRyb2VzdGxlckB1bW9ucy5hYy5iZT4gd3JvdGU6Cj4gCj4gT24gTW9uLCAyOSBEZWMgMjAxNCAw MDo1NTo0MyArMDEwMCwgQ2hyaXN0b3BoZSBUcm9lc3RsZXIgd3JvdGU6Cj4+IAo+PiBJJ2QgbGlr ZSB0byBidWlsZCBhIGxpYnJhcnkgb24gdG9wIG9mIGNvaHR0cCB0aGF0IGNvbW11bmljYXRlcyB3 aXRoIGEKPj4gUkVTVCBBUEkgdXNpbmcgdGhlIENsaWVudCBtb2R1bGUgd2l0aCBhbiBTU0wgZW5k cG9pbnQuICBbLi4uXQo+IAo+IEhpIEFuaWwsCj4gCj4gTmV2ZXIgbWluZCwgSSBmaW5hbGx5IGRl Y2lkZWQgbm90IHRvIHVzZSBhc3luYyDigJQgZm9yIG5vdyBhdCBsZWFzdC4gIEkKPiBjYXNlIHlv dSBhcmUgd29uZGVyaW5nIHdoYXQgdGhpcyBpcyBhYm91dCwgSSBzdGFydGVkIGEgYmluZGluZyB0 byB0aGUKPiBEcm9wYm94IEFQSSA8aHR0cHM6Ly9naXRodWIuY29tL0NocmlzMDAvb2NhbWwtZHJv cGJveD4gd2hpY2ggc2hvdWxkIGJlCj4gdXNhYmxlIGZyb20gTWlyYWdlIOKAlCBzdGlsbCBoYXZl IHRvIGZpZ3VyZSB0aGF0IG91dCB0aG91Z2guICBUaGUgZ29hbAo+IGlzIHRvIGhhdmUgc29tZSBz dHVkZW50cyBmaW5pc2ggaXQuICBNYXliZSBJJ2xsIHRyeSB0byBkZXZlbG9wIGEKPiBmcmVlL2xp YnJlIGNsaWVudCBvbiB0b3Agb2YgaXQg4oCUIHRoYXQgd291bGQgbm90IGh1cnQgSU1ITy4gIEFs c28gYW4KPiBhcHBsaWNhdGlvbiB0byBleGNoYW5nZSBkYXRhIGJldHdlZW4gSXJtaW4gJiBEcm9w Ym94IHdvdWxkIGJlIG5pY2Ug4oCUCj4gYW5kIGEgYnJpZGdlIHRvIGVhc2UgcGVvcGxlIHRvIHN3 aXRjaCB0byBuZXcgdG9vbHMuCgooSnVzdCBkaXNjb3ZlcmVkIHRoZSBmb2xsb3d1cCB0byBteSBw cmV2aW91cyByZXBseSkuCgpUaGlzIGlzIHZlcnkgY29vbCEgIEZyb20gYSBxdWljayBsb29rLCBp dCBhcHBlYXJzIHRoYXQgaWYgeW91IGZ1bmN0b3Jpc2UKb3ZlciBDb2h0dHBfbHd0IGluc3RlYWQg b2YgQ29odHRwX2x3dF91bml4LCB5b3Ugd2lsbCBoYXZlIHRoZSBkZXNpcmVkCk1pcmFnZSBmdW5j dGlvbmFsaXR5LiAgV2UncmUgYWxtb3N0IHJlYWR5IHRvIGludGVncmF0ZSB0aGUgVExTIHN0YWNr CmludG8gdGhlIFhlbiBiYWNrZW5kIChhaW1lZCBmb3IgTWlyYWdlIDIuNS4wKSwgYXQgd2hpY2gg cG9pbnQgd2Ugc2hvdWxkCmJlIGFibGUgdG8gdGVzdCBvdXQgdGhlIERyb3Bib3ggYmluZGluZ3Mg YXMgYSB1bmlrZXJuZWwuCgpJbiB0aGUgbWVhbndoaWxlLCB0aGV5IGNhbiBiZSB0ZXN0ZWQgb24g dGhlIE1pcmFnZSBVbml4IGJhY2tlbmQgdmlhIHRoZQp0dW50YXAgbW9kdWxlIHdpdGggdXNlcnNw YWNlIG5ldHdvcmtpbmcsIG9yIHZpYSBzb2NrZXRzLgoKPiAKPiBQLlMuIEJUVywgd2h5IENvaHR0 cF9sd3RfYm9keSBpbnN0ZWFkIG9mIENvaHR0cF9sd3QuQm9keSA/ICBUaGF0IHdvdWxkCj4gYmUg bW9yZSBpbiBzeW5jIHdpdGggQ29odHRwLkJvZHkgSU1ITy4gIE1vcmUgZG9jdW1lbnRhdGlvbiBv ZiBjb2h0dHAKPiB3b3VsZCBiZSB3ZWxjb21lIEJUVyDigJQgaW4gcGFydGljdWxhciwgdGhlIGRl c2NyaXB0aW9uIGluIE9QQU0gc2hvdWxkCj4gYmUgZHVwbGljYXRlZCBhdCB0aGUgdG9wIG9mIHRo ZSBkb2N1bWVudGF0aW9uIChpdCB3YXMgbm90IGNsZWFyCj4gcmVhZGluZyBpdCBob3cgdG8gYWN0 aXZhdGUgU1NMIGFuZCB3aGF0IGhhcHBlbnMgaWYgaXQgaXMgbm90Cj4gcHJlc2VudCkuICBJIGFs c28gdGhpbmsgYSB3YXkgdG8gY2hlY2sgKGZyb20gY29odHRwKSB3aGV0aGVyIFNTTCBpcwo+IGF2 YWlsYWJsZSB3b3VsZCBiZSBuaWNlLgoKSW5kZWVkLiAgSSdkIHZlcnkgbXVjaCBhcHByZWNpYXRl IGlmIHlvdSBjb3VsZCBjcmVhdGUgaXNzdWVzIGZvciBhbnkKc3VjaCBjb21tZW50cyBvbiBodHRw czovL2dpdGh1Yi5jb20vbWlyYWdlL29jYW1sLWNvaHR0cC9pc3N1ZXMKCkluIHBhcnRpY3VsYXIs IGZ1bmN0aW9uYWxpdHkgc3VjaCBhcyB0aGUgYXZhaWxhYmlsaXR5IG9mIFNTTCBzaG91bGQKYmUg dmVyeSBlYXN5IHRvIHB1dCBpbi4KCj4gCj4gUC5QLlMuIEZvciB0aGUgYWJvdmUgbGlicmFyeSBJ IGFsc28gbmVlZCB0byBwYXJzZSBkYXRlcy4gIEluc3RlYWQgb2YKPiBkdXBsaWNhdGluZyBhbm90 aGVyIGRhdGUgcGFyc2luZyBsaWJyYXJ5IGluIFN5bmRpYyBhbmQgaW4gRHJvcGJveCwgaG93Cj4g YWJvdXQgdG8gbWFrZSBhIG5ldyBvbmUgc3BsaXQgaW4gc3ViLW1vZHVsZXMgYWNjb3JkaW5nIHRv IHRoZQo+IGF2YWlsYWJsZSByZXNvdXJjZXMgKHVuaXgsIG1pcmFnZSwgamF2YXNjcmlwdCk/ICBJ IHNob3VsZCBnbyB1bmRlciB0aGUKPiBvY2FtbC8gdW1icmVsbGEgb24gR2l0aHViIGFuZCBhaW0g dG8gYmVjb21lIHRoZSBzdGFuZGFyZCBodWIgZm9yIGRhdGVzCj4gKG1vZHVsZXMgdG8gY29udmVy dCBiYWNrIGFuZCBmb3J0aCBmcm9tIHRoZSBleGlzdGluZyBvbmVzIHNob3VsZCBiZQo+IHByb3Zp ZGVkKS4gIFdoYXQgZHUgeW91IHRoaW5rPwoKQSBkYXRlIGxpYnJhcnkgd291bGQgYmUgdmVyeSB1 c2VmdWwgaW5kZWVkLiAgVGhlcmUgc2VlbSB0byBiZSBxdWl0ZQphIGZldyBvcHRpb25zIGF2YWls YWJsZSBhbHJlYWR5IHRob3VnaC4uLj8KCkFuaWwKX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9T LWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9j Z2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Sun Apr 19 17:41:24 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 17:41: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 1YjtDg-0001TJ-7o; Sun, 19 Apr 2015 17:41:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjtDe-0001TE-GO for mirageos-devel@lists.xenproject.org; Sun, 19 Apr 2015 17:41:22 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id E0/B2-04861-1C8E3355; Sun, 19 Apr 2015 17:41:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1429465280!17877171!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22739 invoked from network); 19 Apr 2015 17:41:20 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Apr 2015 17:41:20 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 94660f36; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 19 Apr 2015 18:41:20 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: <20150103.174914.2189911392197753803.Christophe.Troestler@umons.ac.be> Date: Sun, 19 Apr 2015 18:41:18 +0100 Message-Id: <9D65A5B6-CB97-46FF-A44F-5B108945094C@recoil.org> References: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> <20150103.174914.2189911392197753803.Christophe.Troestler@umons.ac.be> To: Christophe Troestler X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Generic use of cohttp 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="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMyBKYW4gMjAxNSwgYXQgMTY6NDksIENocmlzdG9waGUgVHJvZXN0bGVyIDxDaHJpc3RvcGhl LlRyb2VzdGxlckB1bW9ucy5hYy5iZT4gd3JvdGU6Cj4gCj4gT24gTW9uLCAyOSBEZWMgMjAxNCAw MDo1NTo0MyArMDEwMCwgQ2hyaXN0b3BoZSBUcm9lc3RsZXIgd3JvdGU6Cj4+IAo+PiBJJ2QgbGlr ZSB0byBidWlsZCBhIGxpYnJhcnkgb24gdG9wIG9mIGNvaHR0cCB0aGF0IGNvbW11bmljYXRlcyB3 aXRoIGEKPj4gUkVTVCBBUEkgdXNpbmcgdGhlIENsaWVudCBtb2R1bGUgd2l0aCBhbiBTU0wgZW5k cG9pbnQuICBbLi4uXQo+IAo+IEhpIEFuaWwsCj4gCj4gTmV2ZXIgbWluZCwgSSBmaW5hbGx5IGRl Y2lkZWQgbm90IHRvIHVzZSBhc3luYyDigJQgZm9yIG5vdyBhdCBsZWFzdC4gIEkKPiBjYXNlIHlv dSBhcmUgd29uZGVyaW5nIHdoYXQgdGhpcyBpcyBhYm91dCwgSSBzdGFydGVkIGEgYmluZGluZyB0 byB0aGUKPiBEcm9wYm94IEFQSSA8aHR0cHM6Ly9naXRodWIuY29tL0NocmlzMDAvb2NhbWwtZHJv cGJveD4gd2hpY2ggc2hvdWxkIGJlCj4gdXNhYmxlIGZyb20gTWlyYWdlIOKAlCBzdGlsbCBoYXZl IHRvIGZpZ3VyZSB0aGF0IG91dCB0aG91Z2guICBUaGUgZ29hbAo+IGlzIHRvIGhhdmUgc29tZSBz dHVkZW50cyBmaW5pc2ggaXQuICBNYXliZSBJJ2xsIHRyeSB0byBkZXZlbG9wIGEKPiBmcmVlL2xp YnJlIGNsaWVudCBvbiB0b3Agb2YgaXQg4oCUIHRoYXQgd291bGQgbm90IGh1cnQgSU1ITy4gIEFs c28gYW4KPiBhcHBsaWNhdGlvbiB0byBleGNoYW5nZSBkYXRhIGJldHdlZW4gSXJtaW4gJiBEcm9w Ym94IHdvdWxkIGJlIG5pY2Ug4oCUCj4gYW5kIGEgYnJpZGdlIHRvIGVhc2UgcGVvcGxlIHRvIHN3 aXRjaCB0byBuZXcgdG9vbHMuCgooSnVzdCBkaXNjb3ZlcmVkIHRoZSBmb2xsb3d1cCB0byBteSBw cmV2aW91cyByZXBseSkuCgpUaGlzIGlzIHZlcnkgY29vbCEgIEZyb20gYSBxdWljayBsb29rLCBp dCBhcHBlYXJzIHRoYXQgaWYgeW91IGZ1bmN0b3Jpc2UKb3ZlciBDb2h0dHBfbHd0IGluc3RlYWQg b2YgQ29odHRwX2x3dF91bml4LCB5b3Ugd2lsbCBoYXZlIHRoZSBkZXNpcmVkCk1pcmFnZSBmdW5j dGlvbmFsaXR5LiAgV2UncmUgYWxtb3N0IHJlYWR5IHRvIGludGVncmF0ZSB0aGUgVExTIHN0YWNr CmludG8gdGhlIFhlbiBiYWNrZW5kIChhaW1lZCBmb3IgTWlyYWdlIDIuNS4wKSwgYXQgd2hpY2gg cG9pbnQgd2Ugc2hvdWxkCmJlIGFibGUgdG8gdGVzdCBvdXQgdGhlIERyb3Bib3ggYmluZGluZ3Mg YXMgYSB1bmlrZXJuZWwuCgpJbiB0aGUgbWVhbndoaWxlLCB0aGV5IGNhbiBiZSB0ZXN0ZWQgb24g dGhlIE1pcmFnZSBVbml4IGJhY2tlbmQgdmlhIHRoZQp0dW50YXAgbW9kdWxlIHdpdGggdXNlcnNw YWNlIG5ldHdvcmtpbmcsIG9yIHZpYSBzb2NrZXRzLgoKPiAKPiBQLlMuIEJUVywgd2h5IENvaHR0 cF9sd3RfYm9keSBpbnN0ZWFkIG9mIENvaHR0cF9sd3QuQm9keSA/ICBUaGF0IHdvdWxkCj4gYmUg bW9yZSBpbiBzeW5jIHdpdGggQ29odHRwLkJvZHkgSU1ITy4gIE1vcmUgZG9jdW1lbnRhdGlvbiBv ZiBjb2h0dHAKPiB3b3VsZCBiZSB3ZWxjb21lIEJUVyDigJQgaW4gcGFydGljdWxhciwgdGhlIGRl c2NyaXB0aW9uIGluIE9QQU0gc2hvdWxkCj4gYmUgZHVwbGljYXRlZCBhdCB0aGUgdG9wIG9mIHRo ZSBkb2N1bWVudGF0aW9uIChpdCB3YXMgbm90IGNsZWFyCj4gcmVhZGluZyBpdCBob3cgdG8gYWN0 aXZhdGUgU1NMIGFuZCB3aGF0IGhhcHBlbnMgaWYgaXQgaXMgbm90Cj4gcHJlc2VudCkuICBJIGFs c28gdGhpbmsgYSB3YXkgdG8gY2hlY2sgKGZyb20gY29odHRwKSB3aGV0aGVyIFNTTCBpcwo+IGF2 YWlsYWJsZSB3b3VsZCBiZSBuaWNlLgoKSW5kZWVkLiAgSSdkIHZlcnkgbXVjaCBhcHByZWNpYXRl IGlmIHlvdSBjb3VsZCBjcmVhdGUgaXNzdWVzIGZvciBhbnkKc3VjaCBjb21tZW50cyBvbiBodHRw czovL2dpdGh1Yi5jb20vbWlyYWdlL29jYW1sLWNvaHR0cC9pc3N1ZXMKCkluIHBhcnRpY3VsYXIs IGZ1bmN0aW9uYWxpdHkgc3VjaCBhcyB0aGUgYXZhaWxhYmlsaXR5IG9mIFNTTCBzaG91bGQKYmUg dmVyeSBlYXN5IHRvIHB1dCBpbi4KCj4gCj4gUC5QLlMuIEZvciB0aGUgYWJvdmUgbGlicmFyeSBJ IGFsc28gbmVlZCB0byBwYXJzZSBkYXRlcy4gIEluc3RlYWQgb2YKPiBkdXBsaWNhdGluZyBhbm90 aGVyIGRhdGUgcGFyc2luZyBsaWJyYXJ5IGluIFN5bmRpYyBhbmQgaW4gRHJvcGJveCwgaG93Cj4g YWJvdXQgdG8gbWFrZSBhIG5ldyBvbmUgc3BsaXQgaW4gc3ViLW1vZHVsZXMgYWNjb3JkaW5nIHRv IHRoZQo+IGF2YWlsYWJsZSByZXNvdXJjZXMgKHVuaXgsIG1pcmFnZSwgamF2YXNjcmlwdCk/ICBJ IHNob3VsZCBnbyB1bmRlciB0aGUKPiBvY2FtbC8gdW1icmVsbGEgb24gR2l0aHViIGFuZCBhaW0g dG8gYmVjb21lIHRoZSBzdGFuZGFyZCBodWIgZm9yIGRhdGVzCj4gKG1vZHVsZXMgdG8gY29udmVy dCBiYWNrIGFuZCBmb3J0aCBmcm9tIHRoZSBleGlzdGluZyBvbmVzIHNob3VsZCBiZQo+IHByb3Zp ZGVkKS4gIFdoYXQgZHUgeW91IHRoaW5rPwoKQSBkYXRlIGxpYnJhcnkgd291bGQgYmUgdmVyeSB1 c2VmdWwgaW5kZWVkLiAgVGhlcmUgc2VlbSB0byBiZSBxdWl0ZQphIGZldyBvcHRpb25zIGF2YWls YWJsZSBhbHJlYWR5IHRob3VnaC4uLj8KCkFuaWwKX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9T LWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9j Z2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Sun Apr 19 17:59:34 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 19 Apr 2015 17:59: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 1YjtVE-0002RL-LQ; Sun, 19 Apr 2015 17:59:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YjtVC-0002RG-Ud for mirageos-devel@lists.xenproject.org; Sun, 19 Apr 2015 17:59:31 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id C4/BE-03284-20DE3355; Sun, 19 Apr 2015 17:59:30 +0000 X-Env-Sender: rudi.grinberg@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1429466367!16988178!1 X-Originating-IP: [209.85.213.172] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5203 invoked from network); 19 Apr 2015 17:59:28 -0000 Received: from mail-ig0-f172.google.com (HELO mail-ig0-f172.google.com) (209.85.213.172) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2015 17:59:28 -0000 Received: by iget9 with SMTP id t9so53413619ige.1 for ; Sun, 19 Apr 2015 10:59:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type; bh=mI60KMc5Ncn9Zq3k2L55OBi8Bba9s9OtmCuXtUX54g0=; b=CSa/qVnulARgGW2qViPLC1PVzc4Pk+i7leiaK0HhE+PwyjeihQoLBatvTeUcjmS1YF L81Xrib2UmeiYJ/JHGc8KWFCH5TIgbQxNR33XLU8x5BzWPNoIre+W3YO79ue+9w8VuKK 1o7OrTO6gDSG9IArDp3zvqRHDTWynocmwH8wUnVLG5mE2YWR24rdSUO9u42SbDb9kjUW yyIwE4jdLjJkzGEhF2Jgi4DpZXZKefT5u/FzUkYYOAGb+8/7f8EFjXuw2ntAs4pA8Ham YdcB0c0fFF9LtTP3M57u/D57XmLo77Z4Nkt+jBDloBB6L2+cVJDd+Q4Gh86C9Rg8w8MU TNYg== X-Received: by 10.43.66.14 with SMTP id xo14mr14582876icb.38.1429466367631; Sun, 19 Apr 2015 10:59:27 -0700 (PDT) Received: from Rudis-MacBook-Pro.local ([66.49.175.19]) by mx.google.com with ESMTPSA id y18sm10158936ioi.18.2015.04.19.10.59.26 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Apr 2015 10:59:27 -0700 (PDT) Date: Sun, 19 Apr 2015 14:03:55 -0400 From: Rudi Grinberg To: Anil Madhavapeddy , Christophe Troestler Message-ID: In-Reply-To: <9D65A5B6-CB97-46FF-A44F-5B108945094C@recoil.org> References: <20141229.005543.466521468899813471.Christophe.Troestler@umons.ac.be> <20150103.174914.2189911392197753803.Christophe.Troestler@umons.ac.be> <9D65A5B6-CB97-46FF-A44F-5B108945094C@recoil.org> X-Mailer: Airmail Beta (301) MIME-Version: 1.0 Cc: mirageos-devel Subject: Re: [MirageOS-devel] Generic use of cohttp 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="===============4585486558014769263==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4585486558014769263== Content-Type: multipart/alternative; boundary="5533ee0b_2afddca0_175" --5533ee0b_2afddca0_175 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Christophe, IMHO, you shouldn=E2=80=99t worry about accommodating async until there=E2= =80=99s some demand for it (and vice versa for lwt if you were an async u= ser). However, I do think that you can make some interface improvements t= o make it a lot easier for potential async users. Request and Response ty= pes are portable between backends in cohttp. Hence exposing them directly= would allow async users to make fire off their own requests. But this do= es have the disadvantage of leaking a larger interface than necessary. Regards, Rudi. On April 19, 2015 at 1:41:35 PM, Anil Madhavapeddy (anil=40recoil.org) wr= ote: On 3 Jan 2015, at 16:49, Christophe Troestler wrote: >=C2=A0 > On Mon, 29 Dec 2014 00:55:43 +0100, Christophe Troestler wrote: >>=C2=A0 >> I'd like to build a library on top of cohttp that communicates with a >> REST API using the Client module with an SSL endpoint. =5B...=5D >=C2=A0 > Hi Anil, >=C2=A0 > Never mind, I finally decided not to use async =E2=80=94 for now at lea= st. I > case you are wondering what this is about, I started a binding to the > Dropbox API which should be > usable from Mirage =E2=80=94 still have to figure that out though. The = goal > is to have some students finish it. Maybe I'll try to develop a > free/libre client on top of it =E2=80=94 that would not hurt IMHO. Also= an > application to exchange data between Irmin & Dropbox would be nice =E2=80= =94 > and a bridge to ease people to switch to new tools. (Just discovered the followup to my previous reply). This is very cool=21 =46rom a quick look, it appears that if you functori= se over Cohttp=5Flwt instead of Cohttp=5Flwt=5Funix, you will have the desir= ed Mirage functionality. We're almost ready to integrate the TLS stack into the Xen backend (aimed for Mirage 2.5.0), at which point we should be able to test out the Dropbox bindings as a unikernel. In the meanwhile, they can be tested on the Mirage Unix backend via the tuntap module with userspace networking, or via sockets. >=C2=A0 > P.S. BTW, why Cohttp=5Flwt=5Fbody instead of Cohttp=5Flwt.Body =3F That= would > be more in sync with Cohttp.Body IMHO. More documentation of cohttp > would be welcome BTW Yes this should be fixed. I can=E2=80=99t count the number of times I=E2=80= =99ve written the alias module Body =3D Cohttp=5Flwt=5Fbody =C2=A0=E2=80=94 in particular, the description in OPAM should > be duplicated at the top of the documentation (it was not clear > reading it how to activate SSL and what happens if it is not > present). I also think a way to check (from cohttp) whether SSL is > available would be nice. Indeed. I'd very much appreciate if you could create issues for any such comments on https://github.com/mirage/ocaml-cohttp/issues In particular, functionality such as the availability of SSL should be very easy to put in. >=C2=A0 > P.P.S. =46or the above library I also need to parse dates. Instead of > duplicating another date parsing library in Syndic and in Dropbox, how > about to make a new one split in sub-modules according to the > available resources (unix, mirage, javascript)=3F I should go under the= > ocaml/ umbrella on Github and aim to become the standard hub for dates > (modules to convert back and forth from the existing ones should be > provided). What du you think=3F A date library would be very useful indeed. There seem to be quite a few options available already though...=3F Anil =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F MirageOS-devel mailing list MirageOS-devel=40lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --5533ee0b_2afddca0_175 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi=2C

Can anyone recommen= d a good Timer library to use with mirage - I need it for firing off events= - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C cyclic etc.

T= hanks=2C
Nick
= --_88c06107-00fa-4c6c-9c28-235372a994a1_-- --===============4977693477939733742== 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 --===============4977693477939733742==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 12:00:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 12:00:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlFoD-0008QM-GW; Thu, 23 Apr 2015 12:00:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlFoC-0008Py-D3 for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 12:00:44 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id A4/F6-26324-BEED8355; Thu, 23 Apr 2015 12:00:43 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1429790442!16762879!1 X-Originating-IP: [157.55.2.16] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4801 invoked from network); 23 Apr 2015 12:00:43 -0000 Received: from dub004-omc3s7.hotmail.com (HELO DUB004-OMC3S7.hotmail.com) (157.55.2.16) by server-14.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 23 Apr 2015 12:00:43 -0000 Received: from DUB128-W17 ([157.55.2.9]) by DUB004-OMC3S7.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Thu, 23 Apr 2015 05:00:42 -0700 X-TMN: [A1a47QbEUGWOx0HtwwON6tqg1Gl1sMdA] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Thu, 23 Apr 2015 12:00:41 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 23 Apr 2015 12:00:42.0592 (UTC) FILETIME=[1F956600:01D07DBD] Subject: [MirageOS-devel] Timer 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="===============4977693477939733742==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4977693477939733742== Content-Type: multipart/alternative; boundary="_88c06107-00fa-4c6c-9c28-235372a994a1_" --_88c06107-00fa-4c6c-9c28-235372a994a1_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C Can anyone recommend a good Timer library to use with mirage - I need it fo= r firing off events - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C c= yclic etc. Thanks=2C Nick = --_88c06107-00fa-4c6c-9c28-235372a994a1_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=2C

Can anyone recommen= d a good Timer library to use with mirage - I need it for firing off events= - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C cyclic etc.

T= hanks=2C
Nick
= --_88c06107-00fa-4c6c-9c28-235372a994a1_-- --===============4977693477939733742== 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 --===============4977693477939733742==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 12:19:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 12:19: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 1YlG66-0000kU-FW; Thu, 23 Apr 2015 12:19:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlG64-0000k0-LJ for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 12:19:12 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id A6/79-23555-F33E8355; Thu, 23 Apr 2015 12:19:11 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1429791549!15494799!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27226 invoked from network); 23 Apr 2015 12:19:10 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2015 12:19:10 -0000 Received: by wgso17 with SMTP id o17so16337792wgs.1 for ; Thu, 23 Apr 2015 05:19:09 -0700 (PDT) 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=4K8wVfErZ6Lyji6W71hPFdzwEV/aQLzmOyD09dRshoE=; b=p10mDXTRI1gjWGRe1aLsxPZMYQRRT1Gl7fryW+pn5FxdoAvGIraxnkN2pvuNHI89RX y5CCtOV+hMFm7hoxbRu8rs6H4fD3Xp/Qvh67J+tbIOgQRU9n3wCRLRusA5/l77z2a0UL 6cF6LB1Zamb37+mKn+W7TJtkfFvJD3vMzcwRUC0qKqUVf+s0BtTHieUe1vkc8BY9wv1+ 1ut8pJoNWtrzNn0P6/VpmSKGe66OIsBaIJG3G+XR1FVq8wmIqBXtUsEQEy4k3O5B2ZVK 2Y2X15MZv8p2E6a+Ev6qL70rtNiVEZ1290VG56c4ioihKcOmMUdinvm/G7GQD83RATTU MBGw== MIME-Version: 1.0 X-Received: by 10.195.18.103 with SMTP id gl7mr4855585wjd.34.1429791549642; Thu, 23 Apr 2015 05:19:09 -0700 (PDT) Received: by 10.27.14.14 with HTTP; Thu, 23 Apr 2015 05:19:09 -0700 (PDT) Date: Thu, 23 Apr 2015 13:19:09 +0100 Message-ID: From: Matthew Gray To: mirageos-devel Subject: [MirageOS-devel] Talking about MirageOS at Devs in the Ditch, May 21st 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="===============3101451178113031753==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3101451178113031753== Content-Type: multipart/alternative; boundary=001a11c28a826b5e3e0514634985 --001a11c28a826b5e3e0514634985 Content-Type: text/plain; charset=UTF-8 Hello all, Just a heads up that I am going to be talking about unikernels and MirageOS a bit at Devs in the Ditch, which is a tech meetup run by 7digital (my employer) The event page is here: http://www.meetup.com/devs-in-the-ditch/events/221972483/ , I can see a few familiar names from this list have already signed up. My talk is going to be quite high-level, and focus on my experiences and motivations for wanting to learn about MirageOS, as well as showing off various cool projects (Jitsu springs to mind) that will hopefully encourages others to explore MirageOS. Anyway, I hope this is an acceptable topic for a beginner like me to talk about! If it's OK, I might run a few of the slides (*) past the list. Looking forward to meeting some of you on the 21st. thanks, Matt (*) which hopefully will be hosted using Mirage! --001a11c28a826b5e3e0514634985 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

Just a heads up that I am go= ing to be talking about unikernels and MirageOS a bit at Devs in the Ditch,= which is a tech meetup run by 7digital (my employer)

<= div>The event page is here:=C2=A0http://www.meetup.com/devs-in-the-ditch/events/= 221972483/ , I can see a few familiar names from this list have already= signed up.

My talk is going to be quite high-leve= l, and focus on my experiences and motivations for wanting to learn about M= irageOS, as well as showing off various cool projects (Jitsu springs to min= d) that will hopefully encourages others to explore MirageOS. Anyway, I hop= e this is an acceptable topic for a beginner like me to talk about! If it&#= 39;s OK, I might run a few of the slides (*) past the list. Looking forward= to meeting some of you on the 21st.

thanks,
=

Matt

(*) which hopefully will = be hosted using Mirage!

--001a11c28a826b5e3e0514634985-- --===============3101451178113031753== 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 --===============3101451178113031753==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 12:19:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 12:19: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 1YlG66-0000kU-FW; Thu, 23 Apr 2015 12:19:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlG64-0000k0-LJ for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 12:19:12 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id A6/79-23555-F33E8355; Thu, 23 Apr 2015 12:19:11 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1429791549!15494799!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27226 invoked from network); 23 Apr 2015 12:19:10 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2015 12:19:10 -0000 Received: by wgso17 with SMTP id o17so16337792wgs.1 for ; Thu, 23 Apr 2015 05:19:09 -0700 (PDT) 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=4K8wVfErZ6Lyji6W71hPFdzwEV/aQLzmOyD09dRshoE=; b=p10mDXTRI1gjWGRe1aLsxPZMYQRRT1Gl7fryW+pn5FxdoAvGIraxnkN2pvuNHI89RX y5CCtOV+hMFm7hoxbRu8rs6H4fD3Xp/Qvh67J+tbIOgQRU9n3wCRLRusA5/l77z2a0UL 6cF6LB1Zamb37+mKn+W7TJtkfFvJD3vMzcwRUC0qKqUVf+s0BtTHieUe1vkc8BY9wv1+ 1ut8pJoNWtrzNn0P6/VpmSKGe66OIsBaIJG3G+XR1FVq8wmIqBXtUsEQEy4k3O5B2ZVK 2Y2X15MZv8p2E6a+Ev6qL70rtNiVEZ1290VG56c4ioihKcOmMUdinvm/G7GQD83RATTU MBGw== MIME-Version: 1.0 X-Received: by 10.195.18.103 with SMTP id gl7mr4855585wjd.34.1429791549642; Thu, 23 Apr 2015 05:19:09 -0700 (PDT) Received: by 10.27.14.14 with HTTP; Thu, 23 Apr 2015 05:19:09 -0700 (PDT) Date: Thu, 23 Apr 2015 13:19:09 +0100 Message-ID: From: Matthew Gray To: mirageos-devel Subject: [MirageOS-devel] Talking about MirageOS at Devs in the Ditch, May 21st 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="===============3101451178113031753==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3101451178113031753== Content-Type: multipart/alternative; boundary=001a11c28a826b5e3e0514634985 --001a11c28a826b5e3e0514634985 Content-Type: text/plain; charset=UTF-8 Hello all, Just a heads up that I am going to be talking about unikernels and MirageOS a bit at Devs in the Ditch, which is a tech meetup run by 7digital (my employer) The event page is here: http://www.meetup.com/devs-in-the-ditch/events/221972483/ , I can see a few familiar names from this list have already signed up. My talk is going to be quite high-level, and focus on my experiences and motivations for wanting to learn about MirageOS, as well as showing off various cool projects (Jitsu springs to mind) that will hopefully encourages others to explore MirageOS. Anyway, I hope this is an acceptable topic for a beginner like me to talk about! If it's OK, I might run a few of the slides (*) past the list. Looking forward to meeting some of you on the 21st. thanks, Matt (*) which hopefully will be hosted using Mirage! --001a11c28a826b5e3e0514634985 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

Just a heads up that I am go= ing to be talking about unikernels and MirageOS a bit at Devs in the Ditch,= which is a tech meetup run by 7digital (my employer)

<= div>The event page is here:=C2=A0http://www.meetup.com/devs-in-the-ditch/events/= 221972483/ , I can see a few familiar names from this list have already= signed up.

My talk is going to be quite high-leve= l, and focus on my experiences and motivations for wanting to learn about M= irageOS, as well as showing off various cool projects (Jitsu springs to min= d) that will hopefully encourages others to explore MirageOS. Anyway, I hop= e this is an acceptable topic for a beginner like me to talk about! If it&#= 39;s OK, I might run a few of the slides (*) past the list. Looking forward= to meeting some of you on the 21st.

thanks,
=

Matt

(*) which hopefully will = be hosted using Mirage!

--001a11c28a826b5e3e0514634985-- --===============3101451178113031753== 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 --===============3101451178113031753==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 12:45:50 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 12:45:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlGVp-0003HF-60; Thu, 23 Apr 2015 12:45:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlGVn-0003H5-TN for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 12:45:48 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id C1/FC-17455-B79E8355; Thu, 23 Apr 2015 12:45:47 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1429793146!16783239!1 X-Originating-IP: [157.55.2.30] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2803 invoked from network); 23 Apr 2015 12:45:46 -0000 Received: from dub004-omc3s21.hotmail.com (HELO DUB004-OMC3S21.hotmail.com) (157.55.2.30) by server-14.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 23 Apr 2015 12:45:46 -0000 Received: from DUB128-W68 ([157.55.2.7]) by DUB004-OMC3S21.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Thu, 23 Apr 2015 05:45:45 -0700 X-TMN: [UPtxDhxyg+LQbuZMIR84VC1S9kikiMBP] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Thu, 23 Apr 2015 12:45:45 +0000 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 23 Apr 2015 12:45:45.0520 (UTC) FILETIME=[6AA77B00:01D07DC3] Subject: Re: [MirageOS-devel] Timer 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="===============5510558633004566706==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5510558633004566706== Content-Type: multipart/alternative; boundary="_1015b5aa-c258-42ac-a184-914336667960_" --_1015b5aa-c258-42ac-a184-914336667960_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable OK - Core.Scheduler should do just fine! From: buzzheavyyear@hotmail.com To: mirageos-devel@lists.xenproject.org Date: Thu=2C 23 Apr 2015 12:00:41 +0000 Subject: [MirageOS-devel] Timer library =0A= =0A= =0A= Hi=2C Can anyone recommend a good Timer library to use with mirage - I need it fo= r firing off events - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C c= yclic etc. Thanks=2C Nick =0A= _______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = = --_1015b5aa-c258-42ac-a184-914336667960_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
OK - Core.Scheduler should do ju= st fine!

From: buzzheavyyear@hotmail.co= m
To: mirageos-devel@lists.xenproject.org
Date: Thu=2C 23 Apr 2015 12= :00:41 +0000
Subject: [MirageOS-devel] Timer library

=0A= =0A= =0A=
Hi=2C

Can anyone recommend a good Timer library to = use with mirage - I need it for firing off events - add=2C stop=2C start=2C= stop=2C pause=2C one-off=2C cyclic etc.

Thanks=2C
Nick
=
=0A=
_______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
=
= --_1015b5aa-c258-42ac-a184-914336667960_-- --===============5510558633004566706== 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 --===============5510558633004566706==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 12:45:50 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 12:45:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlGVp-0003HF-60; Thu, 23 Apr 2015 12:45:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlGVn-0003H5-TN for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 12:45:48 +0000 Received: from [85.158.137.68] by server-1.bemta-3.messagelabs.com id C1/FC-17455-B79E8355; Thu, 23 Apr 2015 12:45:47 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1429793146!16783239!1 X-Originating-IP: [157.55.2.30] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2803 invoked from network); 23 Apr 2015 12:45:46 -0000 Received: from dub004-omc3s21.hotmail.com (HELO DUB004-OMC3S21.hotmail.com) (157.55.2.30) by server-14.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 23 Apr 2015 12:45:46 -0000 Received: from DUB128-W68 ([157.55.2.7]) by DUB004-OMC3S21.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Thu, 23 Apr 2015 05:45:45 -0700 X-TMN: [UPtxDhxyg+LQbuZMIR84VC1S9kikiMBP] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Thu, 23 Apr 2015 12:45:45 +0000 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 23 Apr 2015 12:45:45.0520 (UTC) FILETIME=[6AA77B00:01D07DC3] Subject: Re: [MirageOS-devel] Timer 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="===============5510558633004566706==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5510558633004566706== Content-Type: multipart/alternative; boundary="_1015b5aa-c258-42ac-a184-914336667960_" --_1015b5aa-c258-42ac-a184-914336667960_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable OK - Core.Scheduler should do just fine! From: buzzheavyyear@hotmail.com To: mirageos-devel@lists.xenproject.org Date: Thu=2C 23 Apr 2015 12:00:41 +0000 Subject: [MirageOS-devel] Timer library =0A= =0A= =0A= Hi=2C Can anyone recommend a good Timer library to use with mirage - I need it fo= r firing off events - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C c= yclic etc. Thanks=2C Nick =0A= _______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = = --_1015b5aa-c258-42ac-a184-914336667960_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
OK - Core.Scheduler should do ju= st fine!

From: buzzheavyyear@hotmail.co= m
To: mirageos-devel@lists.xenproject.org
Date: Thu=2C 23 Apr 2015 12= :00:41 +0000
Subject: [MirageOS-devel] Timer library

=0A= =0A= =0A=
Hi=2C

Can anyone recommend a good Timer library to = use with mirage - I need it for firing off events - add=2C stop=2C start=2C= stop=2C pause=2C one-off=2C cyclic etc.

Thanks=2C
Nick
=
=0A=
_______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
=
= --_1015b5aa-c258-42ac-a184-914336667960_-- --===============5510558633004566706== 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 --===============5510558633004566706==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 13:15:26 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 13:15: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 1YlGyO-0004ct-Q4; Thu, 23 Apr 2015 13:15:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlGyN-0004co-Qo for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 13:15:20 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id 27/DA-06072-660F8355; Thu, 23 Apr 2015 13:15:18 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1429794917!20518956!1 X-Originating-IP: [157.55.2.36] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26239 invoked from network); 23 Apr 2015 13:15:17 -0000 Received: from dub004-omc3s27.hotmail.com (HELO DUB004-OMC3S27.hotmail.com) (157.55.2.36) by server-13.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 23 Apr 2015 13:15:17 -0000 Received: from DUB128-W62 ([157.55.2.8]) by DUB004-OMC3S27.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Thu, 23 Apr 2015 06:15:17 -0700 X-TMN: [7mJjZVRBL0fmZRykjqqI+RdLAyolz8pF] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Thu, 23 Apr 2015 13:15:16 +0000 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 23 Apr 2015 13:15:17.0220 (UTC) FILETIME=[8AAB7240:01D07DC7] Subject: Re: [MirageOS-devel] Timer 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="===============0002740134594998302==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0002740134594998302== Content-Type: multipart/alternative; boundary="_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_" --_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Apologies - I'm just creating noise here. Still looking for a decent schedu= ler - it looks as though the Async one is just for unix. From: buzzheavyyear@hotmail.com To: mirageos-devel@lists.xenproject.org Date: Thu=2C 23 Apr 2015 12:45:45 +0000 Subject: Re: [MirageOS-devel] Timer library =0A= =0A= =0A= OK - Core.Scheduler should do just fine! From: buzzheavyyear@hotmail.com To: mirageos-devel@lists.xenproject.org Date: Thu=2C 23 Apr 2015 12:00:41 +0000 Subject: [MirageOS-devel] Timer library =0A= =0A= =0A= Hi=2C Can anyone recommend a good Timer library to use with mirage - I need it fo= r firing off events - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C c= yclic etc. Thanks=2C Nick =0A= _______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = =0A= _______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = = --_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Apologies - I'm just creating no= ise here. Still looking for a decent scheduler - it looks as though the Asy= nc one is just for unix.

From: buzzheav= yyear@hotmail.com
To: mirageos-devel@lists.xenproject.org
Date: Thu= =2C 23 Apr 2015 12:45:45 +0000
Subject: Re: [MirageOS-devel] Timer libra= ry

=0A= =0A= =0A=
OK - Core.Scheduler should do just fine!

From: buzzheavyyear@hotmail.com
To: mirageos-devel= @lists.xenproject.org
Date: Thu=2C 23 Apr 2015 12:00:41 +0000
Subject= : [MirageOS-devel] Timer library

=0A= =0A= =0A=
Hi=2C

Can anyone recommend a good Timer library to = use with mirage - I need it for firing off events - add=2C stop=2C start=2C= stop=2C pause=2C one-off=2C cyclic etc.

Thanks=2C
Nick
=
=0A=
_______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
=
=0A=
_______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
=
= --_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_-- --===============0002740134594998302== 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 --===============0002740134594998302==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 13:15:26 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 13:15: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 1YlGyO-0004ct-Q4; Thu, 23 Apr 2015 13:15:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlGyN-0004co-Qo for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 13:15:20 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id 27/DA-06072-660F8355; Thu, 23 Apr 2015 13:15:18 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1429794917!20518956!1 X-Originating-IP: [157.55.2.36] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26239 invoked from network); 23 Apr 2015 13:15:17 -0000 Received: from dub004-omc3s27.hotmail.com (HELO DUB004-OMC3S27.hotmail.com) (157.55.2.36) by server-13.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 23 Apr 2015 13:15:17 -0000 Received: from DUB128-W62 ([157.55.2.8]) by DUB004-OMC3S27.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Thu, 23 Apr 2015 06:15:17 -0700 X-TMN: [7mJjZVRBL0fmZRykjqqI+RdLAyolz8pF] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Thu, 23 Apr 2015 13:15:16 +0000 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 23 Apr 2015 13:15:17.0220 (UTC) FILETIME=[8AAB7240:01D07DC7] Subject: Re: [MirageOS-devel] Timer 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="===============0002740134594998302==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0002740134594998302== Content-Type: multipart/alternative; boundary="_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_" --_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Apologies - I'm just creating noise here. Still looking for a decent schedu= ler - it looks as though the Async one is just for unix. From: buzzheavyyear@hotmail.com To: mirageos-devel@lists.xenproject.org Date: Thu=2C 23 Apr 2015 12:45:45 +0000 Subject: Re: [MirageOS-devel] Timer library =0A= =0A= =0A= OK - Core.Scheduler should do just fine! From: buzzheavyyear@hotmail.com To: mirageos-devel@lists.xenproject.org Date: Thu=2C 23 Apr 2015 12:00:41 +0000 Subject: [MirageOS-devel] Timer library =0A= =0A= =0A= Hi=2C Can anyone recommend a good Timer library to use with mirage - I need it fo= r firing off events - add=2C stop=2C start=2C stop=2C pause=2C one-off=2C c= yclic etc. Thanks=2C Nick =0A= _______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = =0A= _______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = = --_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Apologies - I'm just creating no= ise here. Still looking for a decent scheduler - it looks as though the Asy= nc one is just for unix.

From: buzzheav= yyear@hotmail.com
To: mirageos-devel@lists.xenproject.org
Date: Thu= =2C 23 Apr 2015 12:45:45 +0000
Subject: Re: [MirageOS-devel] Timer libra= ry

=0A= =0A= =0A=
OK - Core.Scheduler should do just fine!

From: buzzheavyyear@hotmail.com
To: mirageos-devel= @lists.xenproject.org
Date: Thu=2C 23 Apr 2015 12:00:41 +0000
Subject= : [MirageOS-devel] Timer library

=0A= =0A= =0A=
Hi=2C

Can anyone recommend a good Timer library to = use with mirage - I need it for firing off events - add=2C stop=2C start=2C= stop=2C pause=2C one-off=2C cyclic etc.

Thanks=2C
Nick
=
=0A=
_______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
=
=0A=
_______________________________________________=0A= MirageOS-devel mailing list=0A= MirageOS-devel@lists.xenproject.org=0A= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
=
= --_8039805c-3b1d-4ac4-b8bb-cf7d6b23c743_-- --===============0002740134594998302== 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 --===============0002740134594998302==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 13:41:55 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 13:41: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 1YlHO5-0006Jw-Jy; Thu, 23 Apr 2015 13:41:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlHO4-0006Jm-Ec for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 13:41:52 +0000 Received: from [85.158.139.211] by server-10.bemta-5.messagelabs.com id 4D/6D-21049-F96F8355; Thu, 23 Apr 2015 13:41:51 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1429796510!18105221!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9470 invoked from network); 23 Apr 2015 13:41:51 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Apr 2015 13:41:51 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 6c5f2b7e; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 23 Apr 2015 14:41:50 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 23 Apr 2015 14:41:49 +0100 Message-Id: <684F79B3-2E45-4F09-9E6F-3A4F4F497642@recoil.org> References: To: Nick Betteridge X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Timer 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org In Lwt, you can use the core library to do timers by calling OS.sleep and building up the required abstractions. I notice that there is a Unix-only Lwt_timeout library in the distribution: http://ocsigen.org/lwt/2.4.7/api/Lwt_timeout The only use of Lwt_unix in this library is for Lwt_unix.sleep: https://github.com/ocsigen/lwt/blob/master/src/unix/lwt_timeout.ml So we could generalise this by modifying the Lwt_timeout.sleep () function to take a (?sleep) function that is passed in the relevant function. In the case of Mirage, this would be OS.Time.sleep, and in Unix the existing Lwt_unix.sleep. What other requirements do you have? Do you want these timers to be persistent in the case of restarts? -anil > On 23 Apr 2015, at 13:00, Nick Betteridge wrote: > > Hi, > > Can anyone recommend a good Timer library to use with mirage - I need it for firing off events - add, stop, start, stop, pause, one-off, cyclic etc. > > Thanks, > Nick > _______________________________________________ > 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 Thu Apr 23 13:41:55 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 13:41: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 1YlHO5-0006Jw-Jy; Thu, 23 Apr 2015 13:41:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlHO4-0006Jm-Ec for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 13:41:52 +0000 Received: from [85.158.139.211] by server-10.bemta-5.messagelabs.com id 4D/6D-21049-F96F8355; Thu, 23 Apr 2015 13:41:51 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1429796510!18105221!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9470 invoked from network); 23 Apr 2015 13:41:51 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Apr 2015 13:41:51 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 6c5f2b7e; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 23 Apr 2015 14:41:50 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 23 Apr 2015 14:41:49 +0100 Message-Id: <684F79B3-2E45-4F09-9E6F-3A4F4F497642@recoil.org> References: To: Nick Betteridge X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Timer 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org In Lwt, you can use the core library to do timers by calling OS.sleep and building up the required abstractions. I notice that there is a Unix-only Lwt_timeout library in the distribution: http://ocsigen.org/lwt/2.4.7/api/Lwt_timeout The only use of Lwt_unix in this library is for Lwt_unix.sleep: https://github.com/ocsigen/lwt/blob/master/src/unix/lwt_timeout.ml So we could generalise this by modifying the Lwt_timeout.sleep () function to take a (?sleep) function that is passed in the relevant function. In the case of Mirage, this would be OS.Time.sleep, and in Unix the existing Lwt_unix.sleep. What other requirements do you have? Do you want these timers to be persistent in the case of restarts? -anil > On 23 Apr 2015, at 13:00, Nick Betteridge wrote: > > Hi, > > Can anyone recommend a good Timer library to use with mirage - I need it for firing off events - add, stop, start, stop, pause, one-off, cyclic etc. > > Thanks, > Nick > _______________________________________________ > 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 Thu Apr 23 13:43:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 13:43:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlHPO-0006QK-QD; Thu, 23 Apr 2015 13:43:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlHPN-0006Q6-Mh for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 13:43:13 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 31/A3-20070-CE6F8355; Thu, 23 Apr 2015 13:43:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1429796585!10541952!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26365 invoked from network); 23 Apr 2015 13:43:05 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Apr 2015 13:43:05 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id dd0d6f93; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 23 Apr 2015 14:43:05 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 23 Apr 2015 14:43:04 +0100 Message-Id: References: To: Matthew Gray X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Talking about MirageOS at Devs in the Ditch, May 21st 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="===============9104280351899340251==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9104280351899340251== Content-Type: multipart/alternative; boundary="Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B" --Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I'm really looking forward to this! Of course, feel most free to ask = questions on the list as usual with any blockers along the way... -anil > On 23 Apr 2015, at 13:19, Matthew Gray = wrote: >=20 > Hello all, >=20 > Just a heads up that I am going to be talking about unikernels and = MirageOS a bit at Devs in the Ditch, which is a tech meetup run by = 7digital (my employer) >=20 > The event page is here: = http://www.meetup.com/devs-in-the-ditch/events/221972483/ = , I can see = a few familiar names from this list have already signed up. >=20 > My talk is going to be quite high-level, and focus on my experiences = and motivations for wanting to learn about MirageOS, as well as showing = off various cool projects (Jitsu springs to mind) that will hopefully = encourages others to explore MirageOS. Anyway, I hope this is an = acceptable topic for a beginner like me to talk about! If it's OK, I = might run a few of the slides (*) past the list. Looking forward to = meeting some of you on the 21st. >=20 > thanks, >=20 > Matt >=20 > (*) which hopefully will be hosted using Mirage! >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I'm really looking forward to this!  Of course, feel = most free to ask questions on the list as usual with any blockers along = the way...

-anil

On 23 Apr 2015, at 13:19, = Matthew Gray <matthew.thomas.gray@gmail.com> wrote:

Hello all,

Just a heads up that I am going to be talking about = unikernels and MirageOS a bit at Devs in the Ditch, which is a tech = meetup run by 7digital (my employer)

The event page is here: http://www.meetup.com/devs-in-the-ditch/events/221972483/ = , I can see a few familiar names from this list have already signed = up.

My talk is = going to be quite high-level, and focus on my experiences and = motivations for wanting to learn about MirageOS, as well as showing off = various cool projects (Jitsu springs to mind) that will hopefully = encourages others to explore MirageOS. Anyway, I hope this is an = acceptable topic for a beginner like me to talk about! If it's OK, I = might run a few of the slides (*) past the list. Looking forward to = meeting some of you on the 21st.

thanks,

Matt

(*) which hopefully will be hosted = using Mirage!

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

= --Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B-- --===============9104280351899340251== 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 --===============9104280351899340251==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 13:43:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 13:43:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlHPO-0006QK-QD; Thu, 23 Apr 2015 13:43:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlHPN-0006Q6-Mh for mirageos-devel@lists.xenproject.org; Thu, 23 Apr 2015 13:43:13 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 31/A3-20070-CE6F8355; Thu, 23 Apr 2015 13:43:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1429796585!10541952!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26365 invoked from network); 23 Apr 2015 13:43:05 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Apr 2015 13:43:05 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id dd0d6f93; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 23 Apr 2015 14:43:05 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 23 Apr 2015 14:43:04 +0100 Message-Id: References: To: Matthew Gray X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Talking about MirageOS at Devs in the Ditch, May 21st 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="===============9104280351899340251==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9104280351899340251== Content-Type: multipart/alternative; boundary="Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B" --Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I'm really looking forward to this! Of course, feel most free to ask = questions on the list as usual with any blockers along the way... -anil > On 23 Apr 2015, at 13:19, Matthew Gray = wrote: >=20 > Hello all, >=20 > Just a heads up that I am going to be talking about unikernels and = MirageOS a bit at Devs in the Ditch, which is a tech meetup run by = 7digital (my employer) >=20 > The event page is here: = http://www.meetup.com/devs-in-the-ditch/events/221972483/ = , I can see = a few familiar names from this list have already signed up. >=20 > My talk is going to be quite high-level, and focus on my experiences = and motivations for wanting to learn about MirageOS, as well as showing = off various cool projects (Jitsu springs to mind) that will hopefully = encourages others to explore MirageOS. Anyway, I hope this is an = acceptable topic for a beginner like me to talk about! If it's OK, I = might run a few of the slides (*) past the list. Looking forward to = meeting some of you on the 21st. >=20 > thanks, >=20 > Matt >=20 > (*) which hopefully will be hosted using Mirage! >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I'm really looking forward to this!  Of course, feel = most free to ask questions on the list as usual with any blockers along = the way...

-anil

On 23 Apr 2015, at 13:19, = Matthew Gray <matthew.thomas.gray@gmail.com> wrote:

Hello all,

Just a heads up that I am going to be talking about = unikernels and MirageOS a bit at Devs in the Ditch, which is a tech = meetup run by 7digital (my employer)

The event page is here: http://www.meetup.com/devs-in-the-ditch/events/221972483/ = , I can see a few familiar names from this list have already signed = up.

My talk is = going to be quite high-level, and focus on my experiences and = motivations for wanting to learn about MirageOS, as well as showing off = various cool projects (Jitsu springs to mind) that will hopefully = encourages others to explore MirageOS. Anyway, I hope this is an = acceptable topic for a beginner like me to talk about! If it's OK, I = might run a few of the slides (*) past the list. Looking forward to = meeting some of you on the 21st.

thanks,

Matt

(*) which hopefully will be hosted = using Mirage!

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

= --Apple-Mail=_11607865-A18A-46E0-9069-5BEFE957C38B-- --===============9104280351899340251== 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 --===============9104280351899340251==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 23 16:50:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 16:50: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 1YlKKG-0008BZ-Cv; Thu, 23 Apr 2015 16:50:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlKKE-0008BD-JK; Thu, 23 Apr 2015 16:50:06 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 2E/F0-18531-DB229355; Thu, 23 Apr 2015 16:50:05 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1429807805!19337681!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8779 invoked from network); 23 Apr 2015 16:50:05 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2015 16:50:05 -0000 Received: by widdi4 with SMTP id di4so223063313wid.0; Thu, 23 Apr 2015 09:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=4HKdbfLFKv1lHzWpwzwiITu1KAVc1kbhDRvOCWltH5E=; b=mijumsAXy1PbExmDJjYm2SlX322H5CdpKV2yXKOnmlJNvKU6VB7EaYy/UvUple5gql jr/Ya8NtCmBUExFQFJ1RODerb52TsIvtJam2twlG8N4qt26ii2chyCwLckcfxu/tdO+f mRAbivMhZlmL49U7/yso7GqkRrI+nTkW8x8arP/B9mIpRl59tay8w3FDAHNTzEw1cC0L l9g5BY50znapWIDrC/SjOHT/P0hr0bwfvGcKKpIl6bpN4Rul5sx5X8/WmNQApZAjXZBl HJEYNbvetHpYCFjnjaL9PUxUTRXsDrzJylOzLe52eR+ctv1kIhCFI7DApvJPGZBZKRaK FSRA== MIME-Version: 1.0 X-Received: by 10.194.81.104 with SMTP id z8mr7051953wjx.45.1429807804760; Thu, 23 Apr 2015 09:50:04 -0700 (PDT) Received: by 10.194.163.194 with HTTP; Thu, 23 Apr 2015 09:50:04 -0700 (PDT) Date: Thu, 23 Apr 2015 12:50:04 -0400 X-Google-Sender-Auth: -WkIFG2oyz8XU8WCWGDtQIgiyiI Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel , xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org Subject: [MirageOS-devel] Next Document Day Moved to Wednesday, May 6 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 Due to the Hackathon next week, our normal April Document Day is taking a one week bump to May 6. If anyone objects to this date, please let me know. Otherwise, we'll allow those attending the Hackathon to participate in Document Day upon their return. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Also take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Please think about how you can help out. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you on Document Day in #xendocs! _______________________________________________ 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 Apr 23 16:50:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Apr 2015 16:50: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 1YlKKG-0008BZ-Cv; Thu, 23 Apr 2015 16:50:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlKKE-0008BD-JK; Thu, 23 Apr 2015 16:50:06 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 2E/F0-18531-DB229355; Thu, 23 Apr 2015 16:50:05 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1429807805!19337681!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8779 invoked from network); 23 Apr 2015 16:50:05 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2015 16:50:05 -0000 Received: by widdi4 with SMTP id di4so223063313wid.0; Thu, 23 Apr 2015 09:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=4HKdbfLFKv1lHzWpwzwiITu1KAVc1kbhDRvOCWltH5E=; b=mijumsAXy1PbExmDJjYm2SlX322H5CdpKV2yXKOnmlJNvKU6VB7EaYy/UvUple5gql jr/Ya8NtCmBUExFQFJ1RODerb52TsIvtJam2twlG8N4qt26ii2chyCwLckcfxu/tdO+f mRAbivMhZlmL49U7/yso7GqkRrI+nTkW8x8arP/B9mIpRl59tay8w3FDAHNTzEw1cC0L l9g5BY50znapWIDrC/SjOHT/P0hr0bwfvGcKKpIl6bpN4Rul5sx5X8/WmNQApZAjXZBl HJEYNbvetHpYCFjnjaL9PUxUTRXsDrzJylOzLe52eR+ctv1kIhCFI7DApvJPGZBZKRaK FSRA== MIME-Version: 1.0 X-Received: by 10.194.81.104 with SMTP id z8mr7051953wjx.45.1429807804760; Thu, 23 Apr 2015 09:50:04 -0700 (PDT) Received: by 10.194.163.194 with HTTP; Thu, 23 Apr 2015 09:50:04 -0700 (PDT) Date: Thu, 23 Apr 2015 12:50:04 -0400 X-Google-Sender-Auth: -WkIFG2oyz8XU8WCWGDtQIgiyiI Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel , xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org Subject: [MirageOS-devel] Next Document Day Moved to Wednesday, May 6 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 Due to the Hackathon next week, our normal April Document Day is taking a one week bump to May 6. If anyone objects to this date, please let me know. Otherwise, we'll allow those attending the Hackathon to participate in Document Day upon their return. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Also take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Please think about how you can help out. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you on Document Day in #xendocs! _______________________________________________ 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 Apr 24 08:26:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 08:26: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 1YlYwW-00060L-QL; Fri, 24 Apr 2015 08:26:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlYwV-000607-SO for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 08:26:36 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 5E/92-18531-B3EF9355; Fri, 24 Apr 2015 08:26:35 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-7.tower-31.messagelabs.com!1429863993!19468051!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3343 invoked from network); 24 Apr 2015 08:26:34 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Apr 2015 08:26:34 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 420C120722 for ; Fri, 24 Apr 2015 04:26:33 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute6.internal (MEProxy); Fri, 24 Apr 2015 04:26:33 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=gj6afOUy/ns+gbwKF5isDk1R57A=; b=zvpfnD ggJdSVYKXxk9yWMVLiIEN8G47Jebcv230kmFFmDQia8anKKnT1n4otp5oCnt+ANh uB+KU5Phkx4kBntfUz+WqVsuejFrZD/dSHrjzwhuBy9KCtd7ZvImKor88fCIJNN9 JcCH2sk23gp6LDQMOn3+nHVeVmwoAtM/yoUuQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=gj6afOUy/ns+gbw KF5isDk1R57A=; b=kNoGcX8elBn0Xh2xOyhlnaLKah22NXUJHFBIXKYMGIvozZ8 GhsN2tCnzvG7VeoaGHAYVIH75CEVxo8mbbiMn9SG9FTz0KIU28Ahu7mmYGg3GxLg kR73y9Ww6eh4zJrhl/t3MkG7Y047TpdrLZkpKajszCPZZBUAWw+XhJXvDkaA= Received: by web1.nyi.internal (Postfix, from userid 99) id 1A6A8AE764C; Fri, 24 Apr 2015 04:26:33 -0400 (EDT) Message-Id: <1429863993.1502115.258006021.3729E056@webmail.messagingengine.com> X-Sasl-Enc: TsTU4NKcIfIS/3+w8Urs4nashGv55UBohoBP52Qtxu1l 1429863993 From: Magnus Skjegstad To: "mirageos-devel" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-a7964045 In-Reply-To: <127D5328-EF36-4B41-81A3-7A4645E22AAF@recoil.org> References: <4FB55345-C703-4B05-9F42-C05F6FF6A8FB@cam.ac.uk> <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> <1429700393.739884.257042885.0ED0A72F@webmail.messagingengine.com> <127D5328-EF36-4B41-81A3-7A4645E22AAF@recoil.org> Date: Fri, 24 Apr 2015 10:26:33 +0200 Subject: Re: [MirageOS-devel] Jitsu release plan for NSDI 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 22 Apr 2015, at 11:59, Magnus Skjegstad wrote: > I think the easiest solution "for now" is to add gARP support in Jitsu > so that the MAC addresses of booting unikernels are advertised in > advance. The gARP should ideally be sent from Synjitsu though to not > confuse the switch, so we should probably move the code there later. I have implemented a prototype of this as "garpjitsu" here [1] and submitted a PR to synjitsu [2]. The code starts a conduit vchan_direct server to listen for connections from Jitsu. When it receives a mac/ip pair it will send a gratuitous ARP. I have also added support to Jitsu to notify synjitsu every time a new unikernel is booted. The new parameter --synjitsu=[domain name/uuid] can be used to enable this. 1. https://github.com/MagnusS/garpjitsu 2. https://github.com/samoht/synjitsu/pull/1 Magnus _______________________________________________ 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 Apr 24 08:26:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 08:26: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 1YlYwW-00060L-QL; Fri, 24 Apr 2015 08:26:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlYwV-000607-SO for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 08:26:36 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 5E/92-18531-B3EF9355; Fri, 24 Apr 2015 08:26:35 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-7.tower-31.messagelabs.com!1429863993!19468051!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3343 invoked from network); 24 Apr 2015 08:26:34 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Apr 2015 08:26:34 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 420C120722 for ; Fri, 24 Apr 2015 04:26:33 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute6.internal (MEProxy); Fri, 24 Apr 2015 04:26:33 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=gj6afOUy/ns+gbwKF5isDk1R57A=; b=zvpfnD ggJdSVYKXxk9yWMVLiIEN8G47Jebcv230kmFFmDQia8anKKnT1n4otp5oCnt+ANh uB+KU5Phkx4kBntfUz+WqVsuejFrZD/dSHrjzwhuBy9KCtd7ZvImKor88fCIJNN9 JcCH2sk23gp6LDQMOn3+nHVeVmwoAtM/yoUuQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=gj6afOUy/ns+gbw KF5isDk1R57A=; b=kNoGcX8elBn0Xh2xOyhlnaLKah22NXUJHFBIXKYMGIvozZ8 GhsN2tCnzvG7VeoaGHAYVIH75CEVxo8mbbiMn9SG9FTz0KIU28Ahu7mmYGg3GxLg kR73y9Ww6eh4zJrhl/t3MkG7Y047TpdrLZkpKajszCPZZBUAWw+XhJXvDkaA= Received: by web1.nyi.internal (Postfix, from userid 99) id 1A6A8AE764C; Fri, 24 Apr 2015 04:26:33 -0400 (EDT) Message-Id: <1429863993.1502115.258006021.3729E056@webmail.messagingengine.com> X-Sasl-Enc: TsTU4NKcIfIS/3+w8Urs4nashGv55UBohoBP52Qtxu1l 1429863993 From: Magnus Skjegstad To: "mirageos-devel" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-a7964045 In-Reply-To: <127D5328-EF36-4B41-81A3-7A4645E22AAF@recoil.org> References: <4FB55345-C703-4B05-9F42-C05F6FF6A8FB@cam.ac.uk> <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> <1429700393.739884.257042885.0ED0A72F@webmail.messagingengine.com> <127D5328-EF36-4B41-81A3-7A4645E22AAF@recoil.org> Date: Fri, 24 Apr 2015 10:26:33 +0200 Subject: Re: [MirageOS-devel] Jitsu release plan for NSDI 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 22 Apr 2015, at 11:59, Magnus Skjegstad wrote: > I think the easiest solution "for now" is to add gARP support in Jitsu > so that the MAC addresses of booting unikernels are advertised in > advance. The gARP should ideally be sent from Synjitsu though to not > confuse the switch, so we should probably move the code there later. I have implemented a prototype of this as "garpjitsu" here [1] and submitted a PR to synjitsu [2]. The code starts a conduit vchan_direct server to listen for connections from Jitsu. When it receives a mac/ip pair it will send a gratuitous ARP. I have also added support to Jitsu to notify synjitsu every time a new unikernel is booted. The new parameter --synjitsu=[domain name/uuid] can be used to enable this. 1. https://github.com/MagnusS/garpjitsu 2. https://github.com/samoht/synjitsu/pull/1 Magnus _______________________________________________ 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 Apr 24 09:01:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 09:01:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZTy-0007RO-TY; Fri, 24 Apr 2015 09:01:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZTy-0007RI-5I for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 09:01:10 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 80/68-18531-5560A355; Fri, 24 Apr 2015 09:01:09 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1429866068!19460318!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14325 invoked from network); 24 Apr 2015 09:01:08 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2015 09:01:08 -0000 Received: by wgin8 with SMTP id n8so43647476wgi.0 for ; Fri, 24 Apr 2015 02:01:08 -0700 (PDT) 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=CpUaLh63XnNqEopHViPeqSGGg77yAeuF9sujDLjFyYk=; b=lDsGDAbE01GKcgG5HRO5HAC7zlmKtjYkhy4Hi86CXTW7lYQGch6+3xJ8F0BBVCHbTu fZOe6OX+O/yMEiromRHHrZSfvl3+jhvs7vczP6GF0oyGT27wVsegzw3NmQon9RKq+HlS pYj+Kl+vBG+uTcFpY6UZaSLGwtqeKAL47SS/8A69j/wk5fh9HghAvb082ylNx+dJAl46 7r9/ryyGtP5NuyAjETZ8dUK/S/gyrXzGWPX2FkVVmbN3toX5dURjXXBZrW4D3ewUhgj6 0ZzZ7llrviy5nzGhgbXj3MQFosB/xcquXW/P/F9tK8JU+voBDffCsAKWyb/0kusppk7A 6mBw== X-Received: by 10.194.77.230 with SMTP id v6mr13987582wjw.25.1429866068123; Fri, 24 Apr 2015 02:01:08 -0700 (PDT) Received: from [192.168.1.104] ([95.90.209.229]) by mx.google.com with ESMTPSA id i6sm15974212wjf.29.2015.04.24.02.01.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Apr 2015 02:01:07 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> Date: Fri, 24 Apr 2015 11:01:05 +0200 Message-Id: <848C9B76-BE85-40C7-B0D0-6F47AD65E008@gazagnaire.org> References: <4FB55345-C703-4B05-9F42-C05F6FF6A8FB@cam.ac.uk> <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Jitsu release plan for NSDI 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 > Currently Synjitsu requires an older patched TCP/IP stack and the ARP > tables are a bit difficult to set up. It would be nice if we could merge > the patch into the main stack before NSDI and add a way to configure the > ARP tables dynamically, as it would be much easier to install. I've cleaned up the synjitsu patches to mirage-tcpip: the first bunch of them can be upstreamed without issue, the last one adds a KV parameter to the network functor and add a synjitsu mode to the stack (two modes actually: one which listen to SYN packets and write them into the KV store, and one who listen for SYN packets both by listening to the network and by reading into the KV store). https://github.com/mirage/mirage-tcpip/pull/126 I really would like to add some kind of automatic testing before merging this, so I'm working on that. 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 Apr 24 09:01:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 09:01:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZTy-0007RO-TY; Fri, 24 Apr 2015 09:01:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZTy-0007RI-5I for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 09:01:10 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 80/68-18531-5560A355; Fri, 24 Apr 2015 09:01:09 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1429866068!19460318!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14325 invoked from network); 24 Apr 2015 09:01:08 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2015 09:01:08 -0000 Received: by wgin8 with SMTP id n8so43647476wgi.0 for ; Fri, 24 Apr 2015 02:01:08 -0700 (PDT) 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=CpUaLh63XnNqEopHViPeqSGGg77yAeuF9sujDLjFyYk=; b=lDsGDAbE01GKcgG5HRO5HAC7zlmKtjYkhy4Hi86CXTW7lYQGch6+3xJ8F0BBVCHbTu fZOe6OX+O/yMEiromRHHrZSfvl3+jhvs7vczP6GF0oyGT27wVsegzw3NmQon9RKq+HlS pYj+Kl+vBG+uTcFpY6UZaSLGwtqeKAL47SS/8A69j/wk5fh9HghAvb082ylNx+dJAl46 7r9/ryyGtP5NuyAjETZ8dUK/S/gyrXzGWPX2FkVVmbN3toX5dURjXXBZrW4D3ewUhgj6 0ZzZ7llrviy5nzGhgbXj3MQFosB/xcquXW/P/F9tK8JU+voBDffCsAKWyb/0kusppk7A 6mBw== X-Received: by 10.194.77.230 with SMTP id v6mr13987582wjw.25.1429866068123; Fri, 24 Apr 2015 02:01:08 -0700 (PDT) Received: from [192.168.1.104] ([95.90.209.229]) by mx.google.com with ESMTPSA id i6sm15974212wjf.29.2015.04.24.02.01.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Apr 2015 02:01:07 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> Date: Fri, 24 Apr 2015 11:01:05 +0200 Message-Id: <848C9B76-BE85-40C7-B0D0-6F47AD65E008@gazagnaire.org> References: <4FB55345-C703-4B05-9F42-C05F6FF6A8FB@cam.ac.uk> <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Jitsu release plan for NSDI 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 > Currently Synjitsu requires an older patched TCP/IP stack and the ARP > tables are a bit difficult to set up. It would be nice if we could merge > the patch into the main stack before NSDI and add a way to configure the > ARP tables dynamically, as it would be much easier to install. I've cleaned up the synjitsu patches to mirage-tcpip: the first bunch of them can be upstreamed without issue, the last one adds a KV parameter to the network functor and add a synjitsu mode to the stack (two modes actually: one which listen to SYN packets and write them into the KV store, and one who listen for SYN packets both by listening to the network and by reading into the KV store). https://github.com/mirage/mirage-tcpip/pull/126 I really would like to add some kind of automatic testing before merging this, so I'm working on that. 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 Apr 24 09:08:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 09:08:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZax-0007p1-Of; Fri, 24 Apr 2015 09:08:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZax-0007or-4w for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 09:08:23 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id 8F/83-09816-6080A355; Fri, 24 Apr 2015 09:08:22 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1429866500!11770295!1 X-Originating-IP: [209.85.223.170] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23756 invoked from network); 24 Apr 2015 09:08:21 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2015 09:08:21 -0000 Received: by iedfl3 with SMTP id fl3so89295723ied.1 for ; Fri, 24 Apr 2015 02:08:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/r7hxYjALWXelCK/BlmPelrudCxU0reTEzs0bCp1IkQ=; b=CnW/sfIU34fB/jzBnDXMgJ2u1V2H7/5r8Nhxd/1GlB2B7zS+8uxVBvUNQ+OFXcwwSp MtoR0lEqGOdpatGFC7NL2ifeT93Z2M5YQINx1yEAH7Lm0nkp4Do2DAkqIjh9x+u6fxHF /PbwZtoOAKsnmGMboqm51IvcQCUui2hQ6UCJfqt8zRZ4ISMOiecYkEYCA/SvbSU6zbWV ms2apq0Vg4Jc2Fxz8nF1AlpIjgItrM06X2zebJRHX3hNTXnx/dtKJ8mXiHkBFlQFdlcX 0nX9xkQrmxs9TIxHoll2e61DGWmMu4vzWqmQxM0NK/3YCYF2x7+RbssSY9Df2B0wc65J r9wA== X-Gm-Message-State: ALoCoQn8uaqndf2+ZEzmBWc+conYHFSaifatEUnDnCoYgcCtF1ec6ZiMX1On67z95ipzRh778iXZ MIME-Version: 1.0 X-Received: by 10.107.8.7 with SMTP id 7mr9314481ioi.87.1429866500372; Fri, 24 Apr 2015 02:08:20 -0700 (PDT) Received: by 10.36.30.11 with HTTP; Fri, 24 Apr 2015 02:08:20 -0700 (PDT) In-Reply-To: <848C9B76-BE85-40C7-B0D0-6F47AD65E008@gazagnaire.org> References: <4FB55345-C703-4B05-9F42-C05F6FF6A8FB@cam.ac.uk> <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> <848C9B76-BE85-40C7-B0D0-6F47AD65E008@gazagnaire.org> Date: Fri, 24 Apr 2015 11:08:20 +0200 Message-ID: From: Magnus Therning To: Thomas Gazagnaire Cc: MirageOS Devel Subject: Re: [MirageOS-devel] Jitsu release plan for NSDI 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 April 2015 at 11:01, Thomas Gazagnaire wrote: >> Currently Synjitsu requires an older patched TCP/IP stack and the ARP >> tables are a bit difficult to set up. It would be nice if we could merge >> the patch into the main stack before NSDI and add a way to configure the >> ARP tables dynamically, as it would be much easier to install. > > I've cleaned up the synjitsu patches to mirage-tcpip: the first bunch of them can be upstreamed without issue, the last one adds a KV parameter to the network functor and add a synjitsu mode to the stack (two modes actually: one which listen to SYN packets and write them into the KV store, and one who listen for SYN packets both by listening to the network and by reading into the KV store). > > https://github.com/mirage/mirage-tcpip/pull/126 > > I really would like to add some kind of automatic testing before merging this, so I'm working on that. Sounds like a good idea to have that :) Will the automated testing include testing on ARM? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus _______________________________________________ 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 Apr 24 09:08:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 09:08:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZax-0007p1-Of; Fri, 24 Apr 2015 09:08:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlZax-0007or-4w for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 09:08:23 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id 8F/83-09816-6080A355; Fri, 24 Apr 2015 09:08:22 +0000 X-Env-Sender: magnus@therning.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1429866500!11770295!1 X-Originating-IP: [209.85.223.170] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23756 invoked from network); 24 Apr 2015 09:08:21 -0000 Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2015 09:08:21 -0000 Received: by iedfl3 with SMTP id fl3so89295723ied.1 for ; Fri, 24 Apr 2015 02:08:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/r7hxYjALWXelCK/BlmPelrudCxU0reTEzs0bCp1IkQ=; b=CnW/sfIU34fB/jzBnDXMgJ2u1V2H7/5r8Nhxd/1GlB2B7zS+8uxVBvUNQ+OFXcwwSp MtoR0lEqGOdpatGFC7NL2ifeT93Z2M5YQINx1yEAH7Lm0nkp4Do2DAkqIjh9x+u6fxHF /PbwZtoOAKsnmGMboqm51IvcQCUui2hQ6UCJfqt8zRZ4ISMOiecYkEYCA/SvbSU6zbWV ms2apq0Vg4Jc2Fxz8nF1AlpIjgItrM06X2zebJRHX3hNTXnx/dtKJ8mXiHkBFlQFdlcX 0nX9xkQrmxs9TIxHoll2e61DGWmMu4vzWqmQxM0NK/3YCYF2x7+RbssSY9Df2B0wc65J r9wA== X-Gm-Message-State: ALoCoQn8uaqndf2+ZEzmBWc+conYHFSaifatEUnDnCoYgcCtF1ec6ZiMX1On67z95ipzRh778iXZ MIME-Version: 1.0 X-Received: by 10.107.8.7 with SMTP id 7mr9314481ioi.87.1429866500372; Fri, 24 Apr 2015 02:08:20 -0700 (PDT) Received: by 10.36.30.11 with HTTP; Fri, 24 Apr 2015 02:08:20 -0700 (PDT) In-Reply-To: <848C9B76-BE85-40C7-B0D0-6F47AD65E008@gazagnaire.org> References: <4FB55345-C703-4B05-9F42-C05F6FF6A8FB@cam.ac.uk> <1429694519.714897.257028933.47BFBEC7@webmail.messagingengine.com> <848C9B76-BE85-40C7-B0D0-6F47AD65E008@gazagnaire.org> Date: Fri, 24 Apr 2015 11:08:20 +0200 Message-ID: From: Magnus Therning To: Thomas Gazagnaire Cc: MirageOS Devel Subject: Re: [MirageOS-devel] Jitsu release plan for NSDI 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 April 2015 at 11:01, Thomas Gazagnaire wrote: >> Currently Synjitsu requires an older patched TCP/IP stack and the ARP >> tables are a bit difficult to set up. It would be nice if we could merge >> the patch into the main stack before NSDI and add a way to configure the >> ARP tables dynamically, as it would be much easier to install. > > I've cleaned up the synjitsu patches to mirage-tcpip: the first bunch of them can be upstreamed without issue, the last one adds a KV parameter to the network functor and add a synjitsu mode to the stack (two modes actually: one which listen to SYN packets and write them into the KV store, and one who listen for SYN packets both by listening to the network and by reading into the KV store). > > https://github.com/mirage/mirage-tcpip/pull/126 > > I really would like to add some kind of automatic testing before merging this, so I'm working on that. Sounds like a good idea to have that :) Will the automated testing include testing on ARM? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus _______________________________________________ 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 Apr 24 11:42:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 11:42: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 1Ylbzj-0007VJ-Jk; Fri, 24 Apr 2015 11:42:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ylbzh-0007VE-NC for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 11:42:05 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id AC/B2-14044-C0C2A355; Fri, 24 Apr 2015 11:42:04 +0000 X-Env-Sender: psxlco@nottingham.ac.uk X-Msg-Ref: server-7.tower-206.messagelabs.com!1429875723!18417542!1 X-Originating-IP: [128.243.43.129] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8713 invoked from network); 24 Apr 2015 11:42:03 -0000 Received: from uidappmx06.nottingham.ac.uk (HELO uidappmx06.nottingham.ac.uk) (128.243.43.129) by server-7.tower-206.messagelabs.com with SMTP; 24 Apr 2015 11:42:03 -0000 Received: from uidappmx06.nottingham.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 77AB92CA7EE_53A2C0BB for ; Fri, 24 Apr 2015 11:42:03 +0000 (GMT) Received: from smtp3.nottingham.ac.uk (smtp3.nottingham.ac.uk [128.243.44.55]) by uidappmx06.nottingham.ac.uk (Sophos Email Appliance) with ESMTP id B063E2BD3EB_53A2C0AF for ; Fri, 24 Apr 2015 11:42:02 +0000 (GMT) Received: from [10.154.171.22] by smtp3.nottingham.ac.uk with esmtp (Exim 4.85) (envelope-from ) id 1Ylbze-0005D9-3o; Fri, 24 Apr 2015 12:42:02 +0100 Message-ID: <553A2C09.8020009@nottingham.ac.uk> Date: Fri, 24 Apr 2015 12:42:01 +0100 From: Carlos Oviedo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Magnus Skjegstad References: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> In-Reply-To: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> X-Spam-Score: 0.0 (/) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Just-In-Time Summoning of Unikernels 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-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 Magnus, We are interested to know how the VMs that Jitsu boots up get their IP addresses. Are they hardcoded in libvirt domain XML and/or Mirage config file? We are thinking of a dynamic approach where unikernels get their IP from a DHCP server and we wonder how to retrieve their IP. Help will be appreciated, thanks Kind regards On 09/09/14 13:02, Magnus Skjegstad wrote: > I have written a small forwarding DNS server that starts virtual > machines on demand, which may be of interest to this list. The server is > called Jitsu - or Just-In-Time Summoning of Unikernels. > > Before forwarding a DNS query, Jitsu checks if the requested domain > matches a known unikernel. If it does, the unikernel is started and its > IP is returned to the client. Jitsu continues to respond with the IP of > the unikernel for as long as it is running. If no requests have been > received for the domain within a timeout the unikernel is automatically > stopped. > > The code is available here: > https://github.com/MagnusS/jitsu > > Jitsu has been tested with Mirage VMs on a Cubietruck w/Xen and libvirt. > For installing libvirt with Xen-support I recommend following Nick's > instructions: > http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00178.html. > > The code is proof-of-concept at this point, so there is probably plenty > of room for optimizations. Contributions are welcome. > > Magnus > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel -- Carlos Oviedo PhD student Network Systems Group University of Nottingham 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 Apr 24 11:42:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 11:42: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 1Ylbzj-0007VJ-Jk; Fri, 24 Apr 2015 11:42:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ylbzh-0007VE-NC for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 11:42:05 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id AC/B2-14044-C0C2A355; Fri, 24 Apr 2015 11:42:04 +0000 X-Env-Sender: psxlco@nottingham.ac.uk X-Msg-Ref: server-7.tower-206.messagelabs.com!1429875723!18417542!1 X-Originating-IP: [128.243.43.129] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8713 invoked from network); 24 Apr 2015 11:42:03 -0000 Received: from uidappmx06.nottingham.ac.uk (HELO uidappmx06.nottingham.ac.uk) (128.243.43.129) by server-7.tower-206.messagelabs.com with SMTP; 24 Apr 2015 11:42:03 -0000 Received: from uidappmx06.nottingham.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 77AB92CA7EE_53A2C0BB for ; Fri, 24 Apr 2015 11:42:03 +0000 (GMT) Received: from smtp3.nottingham.ac.uk (smtp3.nottingham.ac.uk [128.243.44.55]) by uidappmx06.nottingham.ac.uk (Sophos Email Appliance) with ESMTP id B063E2BD3EB_53A2C0AF for ; Fri, 24 Apr 2015 11:42:02 +0000 (GMT) Received: from [10.154.171.22] by smtp3.nottingham.ac.uk with esmtp (Exim 4.85) (envelope-from ) id 1Ylbze-0005D9-3o; Fri, 24 Apr 2015 12:42:02 +0100 Message-ID: <553A2C09.8020009@nottingham.ac.uk> Date: Fri, 24 Apr 2015 12:42:01 +0100 From: Carlos Oviedo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Magnus Skjegstad References: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> In-Reply-To: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> X-Spam-Score: 0.0 (/) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Just-In-Time Summoning of Unikernels 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-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 Magnus, We are interested to know how the VMs that Jitsu boots up get their IP addresses. Are they hardcoded in libvirt domain XML and/or Mirage config file? We are thinking of a dynamic approach where unikernels get their IP from a DHCP server and we wonder how to retrieve their IP. Help will be appreciated, thanks Kind regards On 09/09/14 13:02, Magnus Skjegstad wrote: > I have written a small forwarding DNS server that starts virtual > machines on demand, which may be of interest to this list. The server is > called Jitsu - or Just-In-Time Summoning of Unikernels. > > Before forwarding a DNS query, Jitsu checks if the requested domain > matches a known unikernel. If it does, the unikernel is started and its > IP is returned to the client. Jitsu continues to respond with the IP of > the unikernel for as long as it is running. If no requests have been > received for the domain within a timeout the unikernel is automatically > stopped. > > The code is available here: > https://github.com/MagnusS/jitsu > > Jitsu has been tested with Mirage VMs on a Cubietruck w/Xen and libvirt. > For installing libvirt with Xen-support I recommend following Nick's > instructions: > http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00178.html. > > The code is proof-of-concept at this point, so there is probably plenty > of room for optimizations. Contributions are welcome. > > Magnus > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel -- Carlos Oviedo PhD student Network Systems Group University of Nottingham 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 Apr 24 12:02:31 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 12:02: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 1YlcJM-0000H1-PC; Fri, 24 Apr 2015 12:02:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlcJL-0000Gv-SV for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 12:02:24 +0000 Received: from [193.109.254.147] by server-11.bemta-14.messagelabs.com id 62/29-22533-FC03A355; Fri, 24 Apr 2015 12:02:23 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-11.tower-27.messagelabs.com!1429876941!8498197!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2799 invoked from network); 24 Apr 2015 12:02:22 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Apr 2015 12:02:22 -0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id A794420F2B for ; Fri, 24 Apr 2015 08:02:21 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute2.internal (MEProxy); Fri, 24 Apr 2015 08:02:21 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=k/PabBKxu/mhNpkvqPhtGobk7as=; b=vv72Y2 Su+7JECLdntFyN2oFEfvpHDkHwJmmudloqhZtTmHhqVd1uMISsburptu9zEnb1H4 H5NEZ3ON9mlZIMKFtzwlNEUK/eajm05caNxzCGl89wgnfpYWLJgcljiw8bhavNkj ctKsOD2v2poy98TkkTMrAyeBfmtcbysLEpGYI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=k/PabBKxu/mhNpk vqPhtGobk7as=; b=tEkjd75fc4dM+t8MiyZ8mQR5y8PziViCmXnUKT9lN2o/ugd 1Ybwy3gFNsD66TS6S3Auw7Haq4JipNu/JlMALly6738nj9b1EkWB4C8Oq3dDFclA Z03NfZcwkLej2OENItRayKJtNe7vVJEO2P1+40w5eq8zon0nxKgtaMxKU6Gs= Received: by web1.nyi.internal (Postfix, from userid 99) id 7EE30AE795E; Fri, 24 Apr 2015 08:02:21 -0400 (EDT) Message-Id: <1429876941.1555527.258069953.53A2EF57@webmail.messagingengine.com> X-Sasl-Enc: Hi4AFZ6hV8rpvrXvXkm1Ltn1z6bj4/I+JB1IWmjM2Xd9 1429876941 From: Magnus Skjegstad To: Carlos Oviedo MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-a7964045 Date: Fri, 24 Apr 2015 14:02:21 +0200 In-Reply-To: <553A2C09.8020009@nottingham.ac.uk> References: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> <553A2C09.8020009@nottingham.ac.uk> Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Just-In-Time Summoning of Unikernels 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, 24 Apr 2015, at 13:42, Carlos Oviedo wrote: > Hi Magnus, > > We are interested to know how the VMs that Jitsu boots up get their IP > addresses. Are they hardcoded in libvirt domain XML and/or Mirage config > file? > We are thinking of a dynamic approach where unikernels get their IP from > a DHCP server and we wonder how to retrieve their IP. > Help will be appreciated, thanks Jitsu has to know the IP and MAC addresses of the unikernels it controls in advance, as it sends the DNS reply earlier than the unikernel would receive a DHCP address. Currently IP addresses are set manually in both Jitsu (on the command line) and the unikernel (in config.ml). It would be possible to extend Jitsu to allocate IP addresses dynamically, for example by passing an IP address as a boot option to the unikernel (see e.g. https://github.com/mirage/mirage-bootvar-xen). Jitsu could then be configured to control a pool of static IP addresses or to automatically request them from a local DHCP server on behalf of the unikernels. Magnus _______________________________________________ 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 Apr 24 12:02:31 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 12:02: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 1YlcJM-0000H1-PC; Fri, 24 Apr 2015 12:02:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlcJL-0000Gv-SV for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 12:02:24 +0000 Received: from [193.109.254.147] by server-11.bemta-14.messagelabs.com id 62/29-22533-FC03A355; Fri, 24 Apr 2015 12:02:23 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-11.tower-27.messagelabs.com!1429876941!8498197!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2799 invoked from network); 24 Apr 2015 12:02:22 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Apr 2015 12:02:22 -0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id A794420F2B for ; Fri, 24 Apr 2015 08:02:21 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute2.internal (MEProxy); Fri, 24 Apr 2015 08:02:21 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=k/PabBKxu/mhNpkvqPhtGobk7as=; b=vv72Y2 Su+7JECLdntFyN2oFEfvpHDkHwJmmudloqhZtTmHhqVd1uMISsburptu9zEnb1H4 H5NEZ3ON9mlZIMKFtzwlNEUK/eajm05caNxzCGl89wgnfpYWLJgcljiw8bhavNkj ctKsOD2v2poy98TkkTMrAyeBfmtcbysLEpGYI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=k/PabBKxu/mhNpk vqPhtGobk7as=; b=tEkjd75fc4dM+t8MiyZ8mQR5y8PziViCmXnUKT9lN2o/ugd 1Ybwy3gFNsD66TS6S3Auw7Haq4JipNu/JlMALly6738nj9b1EkWB4C8Oq3dDFclA Z03NfZcwkLej2OENItRayKJtNe7vVJEO2P1+40w5eq8zon0nxKgtaMxKU6Gs= Received: by web1.nyi.internal (Postfix, from userid 99) id 7EE30AE795E; Fri, 24 Apr 2015 08:02:21 -0400 (EDT) Message-Id: <1429876941.1555527.258069953.53A2EF57@webmail.messagingengine.com> X-Sasl-Enc: Hi4AFZ6hV8rpvrXvXkm1Ltn1z6bj4/I+JB1IWmjM2Xd9 1429876941 From: Magnus Skjegstad To: Carlos Oviedo MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-a7964045 Date: Fri, 24 Apr 2015 14:02:21 +0200 In-Reply-To: <553A2C09.8020009@nottingham.ac.uk> References: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> <553A2C09.8020009@nottingham.ac.uk> Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Just-In-Time Summoning of Unikernels 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, 24 Apr 2015, at 13:42, Carlos Oviedo wrote: > Hi Magnus, > > We are interested to know how the VMs that Jitsu boots up get their IP > addresses. Are they hardcoded in libvirt domain XML and/or Mirage config > file? > We are thinking of a dynamic approach where unikernels get their IP from > a DHCP server and we wonder how to retrieve their IP. > Help will be appreciated, thanks Jitsu has to know the IP and MAC addresses of the unikernels it controls in advance, as it sends the DNS reply earlier than the unikernel would receive a DHCP address. Currently IP addresses are set manually in both Jitsu (on the command line) and the unikernel (in config.ml). It would be possible to extend Jitsu to allocate IP addresses dynamically, for example by passing an IP address as a boot option to the unikernel (see e.g. https://github.com/mirage/mirage-bootvar-xen). Jitsu could then be configured to control a pool of static IP addresses or to automatically request them from a local DHCP server on behalf of the unikernels. Magnus _______________________________________________ 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 Apr 24 14:47:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 14:47: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 1YletI-00065g-NQ; Fri, 24 Apr 2015 14:47:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YletH-00065Z-9V for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 14:47:39 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 80/57-23555-A875A355; Fri, 24 Apr 2015 14:47:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1429886857!11807835!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16557 invoked from network); 24 Apr 2015 14:47:37 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2015 14:47:37 -0000 Received: by wgen6 with SMTP id n6so53183531wge.3 for ; Fri, 24 Apr 2015 07:47:37 -0700 (PDT) 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=g/4QhxokXQd/Y84NYxvUWLNOhNILniLOd8W4um7chk4=; b=dX29gGezfB6/26o0bjXusne0qblm75lDAGvbi5bGnLnVqMqjblfaFpQP5udoZMLU+Q 1OFDp0sXUpi7MFKc0Jk96j5JOv0+s9Zq01YKVrVB9KxpKVxN17u502bRFcJyiZ3cHP7W 0vhCRK3hFMV3+00BdjU4tN/Dy2WEiSMYqEg7m1vq9KGRrG1BiKh0i1+ZLUdxMUfjzPGY CauJc8vZt0alOrzwyHBHFDDgyOHhSnFX4lAyPnV6InnP1bTH2NR0/dRcUoiwTFHePiAe +z7ACC0ZYBJqRp8vxXWJMrTXwOpaW8xGFBXQTn4+olaewrcOcax1ZNRGrE8SG7hIz6Rn O5UQ== X-Received: by 10.194.187.16 with SMTP id fo16mr16964116wjc.86.1429886857573; Fri, 24 Apr 2015 07:47:37 -0700 (PDT) Received: from [192.168.1.104] ([95.90.209.229]) by mx.google.com with ESMTPSA id kc4sm17206489wjc.2.2015.04.24.07.47.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Apr 2015 07:47:36 -0700 (PDT) From: Thomas Gazagnaire Message-Id: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> Date: Fri, 24 Apr 2015 16:47:34 +0200 To: Mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] Irmin watch API 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 just merged the new watch API into the master branch of Irmin and I've updated the online docs. Feedback is welcome, the new functions are described on the related pull request [1]. Best, Thomas [1] https://github.com/mirage/irmin/pull/187 _______________________________________________ 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 Apr 24 14:47:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 24 Apr 2015 14:47: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 1YletI-00065g-NQ; Fri, 24 Apr 2015 14:47:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YletH-00065Z-9V for mirageos-devel@lists.xenproject.org; Fri, 24 Apr 2015 14:47:39 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 80/57-23555-A875A355; Fri, 24 Apr 2015 14:47:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1429886857!11807835!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16557 invoked from network); 24 Apr 2015 14:47:37 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2015 14:47:37 -0000 Received: by wgen6 with SMTP id n6so53183531wge.3 for ; Fri, 24 Apr 2015 07:47:37 -0700 (PDT) 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=g/4QhxokXQd/Y84NYxvUWLNOhNILniLOd8W4um7chk4=; b=dX29gGezfB6/26o0bjXusne0qblm75lDAGvbi5bGnLnVqMqjblfaFpQP5udoZMLU+Q 1OFDp0sXUpi7MFKc0Jk96j5JOv0+s9Zq01YKVrVB9KxpKVxN17u502bRFcJyiZ3cHP7W 0vhCRK3hFMV3+00BdjU4tN/Dy2WEiSMYqEg7m1vq9KGRrG1BiKh0i1+ZLUdxMUfjzPGY CauJc8vZt0alOrzwyHBHFDDgyOHhSnFX4lAyPnV6InnP1bTH2NR0/dRcUoiwTFHePiAe +z7ACC0ZYBJqRp8vxXWJMrTXwOpaW8xGFBXQTn4+olaewrcOcax1ZNRGrE8SG7hIz6Rn O5UQ== X-Received: by 10.194.187.16 with SMTP id fo16mr16964116wjc.86.1429886857573; Fri, 24 Apr 2015 07:47:37 -0700 (PDT) Received: from [192.168.1.104] ([95.90.209.229]) by mx.google.com with ESMTPSA id kc4sm17206489wjc.2.2015.04.24.07.47.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Apr 2015 07:47:36 -0700 (PDT) From: Thomas Gazagnaire Message-Id: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> Date: Fri, 24 Apr 2015 16:47:34 +0200 To: Mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] Irmin watch API 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 just merged the new watch API into the master branch of Irmin and I've updated the online docs. Feedback is welcome, the new functions are described on the related pull request [1]. Best, Thomas [1] https://github.com/mirage/irmin/pull/187 _______________________________________________ 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 Apr 25 09:46:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 25 Apr 2015 09:46: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 1YlwfJ-0002rh-E7; Sat, 25 Apr 2015 09:46:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlwfI-0002rc-Ri for mirageos-devel@lists.xenproject.org; Sat, 25 Apr 2015 09:46:24 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id D6/29-23555-0726B355; Sat, 25 Apr 2015 09:46:24 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1429955183!19825044!1 X-Originating-IP: [209.85.217.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17181 invoked from network); 25 Apr 2015 09:46:23 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Apr 2015 09:46:23 -0000 Received: by lbcga7 with SMTP id ga7so52461154lbc.1 for ; Sat, 25 Apr 2015 02:46:22 -0700 (PDT) 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=Swe0rim1rXwHKLENchwJv0e9sPDNCrk5BxARnw71r+Y=; b=Qci3Qglxduxv19vKXP/d4FA3Gt5PXCpp1vr5Cvb0GIdjb2XKMyberSU01o5e7EM0KR 3DTnX1NY0la6jHwYEEMs1wyTVk/xZadZZXX2jqYdqGHaBtYx2nENIqfC8a9W3o3OmBro zpsAeOkR4Sk7vkk2W1Uid/jpP2dN+jG+v3aSntmeJPEQYHd4VvrPGzDqbgTpgH3GBynr 567j3fpfq7fwO8wEA0d1RfUBa8y1G4EnIb4Vc1nWEx04WV68616aw4zmcpuOYNzSM4hr NQTA0+jbZaJHwPefCkePcWA1QWj+tgAXKQpcYyYVvHFAkZscA6EdIYZwuTmlt3Jya3Jp 6XUA== MIME-Version: 1.0 X-Received: by 10.112.162.167 with SMTP id yb7mr2201061lbb.121.1429955182601; Sat, 25 Apr 2015 02:46:22 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sat, 25 Apr 2015 02:46:22 -0700 (PDT) In-Reply-To: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> Date: Sat, 25 Apr 2015 10:46:22 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 April 2015 at 15:47, Thomas Gazagnaire wrote: > I've just merged the new watch API into the master branch of Irmin and I've updated the online docs. > > Feedback is welcome, the new functions are described on the related pull request [1]. Some more documentation would be useful. Currently, I see: val watch_head: t -> ?init:head -> (head diff -> unit Lwt.t) -> (unit -> unit Lwt.t) Lwt.t (** [watch_tag t f] calls [f] every time the contents of [t]'s tag is updated. Do nothing if [t] is not persistent. Return a clean-up function to remove the watch handler. {b Note:} even [f] might skip some head updates, it will never be called concurrently: all consecutive calls to [f] are done in sequence, so we ensure that the previous one ended before calling the next one. *) What does the "init" argument do? Will the callback be called immediately with the current value if it's not given? What's the recommended race-free way to start watching a branch? Currently (with the old API) I do: let watch_tags = I.watch_head (store "Watch branch") in I.head (store "Get latest commit") >>= ... initial head ... let head_id = ref (Some initial_head_id) in async (fun () -> watch_tags |> Lwt_stream.iter_s (function ... I.head (store "Get latest commit") >>= fun new_head_id -> if new_head_id <> !head_id then ( head_id := new_head_id ) ) ) Here, I'm assuming that any change made after I.watch_head returns will result in the callback being called. If the head has changed by the time the initial I.head thread returns then the callback might get called unnecessarily, but that's OK. How should this be done with the new API? I'm guessing something like: 1. Read the current head into a ref. 2. Call I.watch_head with a callback to update the ref. 3. Read the current head again in case it updated between (1) and (2). Is that right? -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 25 09:46:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 25 Apr 2015 09:46: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 1YlwfJ-0002rh-E7; Sat, 25 Apr 2015 09:46:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YlwfI-0002rc-Ri for mirageos-devel@lists.xenproject.org; Sat, 25 Apr 2015 09:46:24 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id D6/29-23555-0726B355; Sat, 25 Apr 2015 09:46:24 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1429955183!19825044!1 X-Originating-IP: [209.85.217.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17181 invoked from network); 25 Apr 2015 09:46:23 -0000 Received: from mail-lb0-f177.google.com (HELO mail-lb0-f177.google.com) (209.85.217.177) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Apr 2015 09:46:23 -0000 Received: by lbcga7 with SMTP id ga7so52461154lbc.1 for ; Sat, 25 Apr 2015 02:46:22 -0700 (PDT) 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=Swe0rim1rXwHKLENchwJv0e9sPDNCrk5BxARnw71r+Y=; b=Qci3Qglxduxv19vKXP/d4FA3Gt5PXCpp1vr5Cvb0GIdjb2XKMyberSU01o5e7EM0KR 3DTnX1NY0la6jHwYEEMs1wyTVk/xZadZZXX2jqYdqGHaBtYx2nENIqfC8a9W3o3OmBro zpsAeOkR4Sk7vkk2W1Uid/jpP2dN+jG+v3aSntmeJPEQYHd4VvrPGzDqbgTpgH3GBynr 567j3fpfq7fwO8wEA0d1RfUBa8y1G4EnIb4Vc1nWEx04WV68616aw4zmcpuOYNzSM4hr NQTA0+jbZaJHwPefCkePcWA1QWj+tgAXKQpcYyYVvHFAkZscA6EdIYZwuTmlt3Jya3Jp 6XUA== MIME-Version: 1.0 X-Received: by 10.112.162.167 with SMTP id yb7mr2201061lbb.121.1429955182601; Sat, 25 Apr 2015 02:46:22 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sat, 25 Apr 2015 02:46:22 -0700 (PDT) In-Reply-To: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> Date: Sat, 25 Apr 2015 10:46:22 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 April 2015 at 15:47, Thomas Gazagnaire wrote: > I've just merged the new watch API into the master branch of Irmin and I've updated the online docs. > > Feedback is welcome, the new functions are described on the related pull request [1]. Some more documentation would be useful. Currently, I see: val watch_head: t -> ?init:head -> (head diff -> unit Lwt.t) -> (unit -> unit Lwt.t) Lwt.t (** [watch_tag t f] calls [f] every time the contents of [t]'s tag is updated. Do nothing if [t] is not persistent. Return a clean-up function to remove the watch handler. {b Note:} even [f] might skip some head updates, it will never be called concurrently: all consecutive calls to [f] are done in sequence, so we ensure that the previous one ended before calling the next one. *) What does the "init" argument do? Will the callback be called immediately with the current value if it's not given? What's the recommended race-free way to start watching a branch? Currently (with the old API) I do: let watch_tags = I.watch_head (store "Watch branch") in I.head (store "Get latest commit") >>= ... initial head ... let head_id = ref (Some initial_head_id) in async (fun () -> watch_tags |> Lwt_stream.iter_s (function ... I.head (store "Get latest commit") >>= fun new_head_id -> if new_head_id <> !head_id then ( head_id := new_head_id ) ) ) Here, I'm assuming that any change made after I.watch_head returns will result in the callback being called. If the head has changed by the time the initial I.head thread returns then the callback might get called unnecessarily, but that's OK. How should this be done with the new API? I'm guessing something like: 1. Read the current head into a ref. 2. Call I.watch_head with a callback to update the ref. 3. Read the current head again in case it updated between (1) and (2). Is that right? -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 26 17:06:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 17:06: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 1YmQ0s-0006jj-5u; Sun, 26 Apr 2015 17:06:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmQ0q-0006je-Bk for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 17:06:36 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 4F/45-23555-B1B1D355; Sun, 26 Apr 2015 17:06:35 +0000 X-Env-Sender: trevorsummerssmith@gmail.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1430067993!20027928!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9080 invoked from network); 26 Apr 2015 17:06:33 -0000 Received: from mail-qk0-f173.google.com (HELO mail-qk0-f173.google.com) (209.85.220.173) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 17:06:33 -0000 Received: by qku63 with SMTP id 63so52423654qku.3 for ; Sun, 26 Apr 2015 10:06:32 -0700 (PDT) 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=QfQOR4fhwIilB5OpDnGoLCvdDjXLm11f/f5SldgZwLc=; b=h9mBPjgEbVyUhjjNwYKIwZfArDyzeOEdYG3SPRGo2+kgOG6NA9qKMCqnZTnHMiverA HrHcuN+Gt+1aG+K08hJrEr/0syzE2b4l9IyNRSKQGqoB9Ipt5/tOPiUtpuSBU6rcMULB 6dKoFcz/acsX+h+uyDI4r/ur/SoRMSjz475Yxx3MR1Qosiw4HjBfjpmq3c3XSjaoNfxi gYDMhlf5KIkcCbExMELRQNNM5PeE5+vZHZw6P1dEATjYZHSj6AINKCd2inKHul67OrzP sC1FzfADzNMLe8gx/3LjIbiWNuVtW4TZPQiA6D6LUCVxqcNlghqLM3ghFn15B+ZzQaW8 qr0w== MIME-Version: 1.0 X-Received: by 10.140.150.73 with SMTP id 70mr5530060qhw.10.1430067992826; Sun, 26 Apr 2015 10:06:32 -0700 (PDT) Received: by 10.229.250.2 with HTTP; Sun, 26 Apr 2015 10:06:32 -0700 (PDT) Date: Sun, 26 Apr 2015 13:06:32 -0400 Message-ID: From: Trevor Smith To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Cohttp and Higher Level Client 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="===============8639821061464848813==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8639821061464848813== Content-Type: multipart/alternative; boundary=001a1135531ab79b320514a3a6b8 --001a1135531ab79b320514a3a6b8 Content-Type: text/plain; charset=UTF-8 Hi all, tl;dr I would like to create a more feature-ful and higher level http client library. Should this go into cohttp or be a separate library? I would suggest it is a separate library. I would like to create a higher level http client to work with Async. I would excited to have this support LWT as well if others wanted to do that work. My personal needs at the moment are connection pooling, more sugar for ease of use (think ease of use of Python's Requests http://docs.python-requests.org/en/latest/), much more extensible (think http://www.intridea.com/blog/2012/3/12/faraday-one-http-client-to-rule-them-all). There's other things that one wants in a client library: dealing appropriately with cache headers, cookies and redirect handling that would need to be added at some point. It seems that Cohttp's current interface is low level, and that there's already been discussion suggesting that the complexity of implementing a http client should be part of another library ( https://github.com/mirage/ocaml-cohttp/issues/76). I would suggest that I begin work on this new library because it will be quicker to get the details ironed out without taking up the current maintainers time. I would see this library's relationship to Cohttp similar to https://github.com/rgrinberg/opium. There will need to be multiple changes to the current Cohttp Async client to support something like this, but I would try and keep those minimal, with the idea being that Cohttp stays the bedrock of http implementations for both client and servers. If at some point, it made sense to merge the efforts I'd be open to that. Also if the current maintainers feel strongly that this work should all go into Cohttp I am happy to contribute it there. Eager to hear your thoughts. Thanks. Trevor --001a1135531ab79b320514a3a6b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

tl;dr I would like to create a = more feature-ful and higher level http client library. Should this go into = cohttp or be a separate library? I would suggest it is a separate library.<= /div>

I would like to create a higher level http client = to work with Async. I would excited to have this support LWT as well if oth= ers wanted to do that work. My personal needs at the moment are connection = pooling, more sugar for ease of use (think ease of use of Python's Requ= ests http://docs.pyt= hon-requests.org/en/latest/), much more extensible (think=C2=A0http://www.intridea.com/blog/2012/3/12/faraday-one-http-client-to= -rule-them-all). There's other things that one wants in a client li= brary: dealing appropriately with cache headers, cookies and redirect handl= ing that would need to be added at some point.

It = seems that Cohttp's current interface is low level, and that there'= s already been discussion suggesting that the complexity of implementing a = http client should be part of another library (https://github.com/mirage/ocaml-cohttp/iss= ues/76).

I would suggest that I begin work on = this new library because it will be quicker to get the details ironed out w= ithout taking up the current maintainers time. I would see this library'= ;s relationship to Cohttp similar to https://github.com/rgrinberg/opium.

T= here will need to be multiple changes to the current Cohttp Async client to= support something like this, but I would try and keep those minimal, with = the idea being that Cohttp stays the bedrock of http implementations for bo= th client and servers. If at some point, it made sense to merge the efforts= I'd be open to that. Also if the current maintainers feel strongly tha= t this work should all go into Cohttp I am happy to contribute it there.

Eager to hear your thoughts. Thanks.

<= /div>
Trevor
--001a1135531ab79b320514a3a6b8-- --===============8639821061464848813== 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 --===============8639821061464848813==-- From mirageos-devel-bounces@lists.xenproject.org Sun Apr 26 17:06:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 17:06: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 1YmQ0s-0006jj-5u; Sun, 26 Apr 2015 17:06:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmQ0q-0006je-Bk for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 17:06:36 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 4F/45-23555-B1B1D355; Sun, 26 Apr 2015 17:06:35 +0000 X-Env-Sender: trevorsummerssmith@gmail.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1430067993!20027928!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9080 invoked from network); 26 Apr 2015 17:06:33 -0000 Received: from mail-qk0-f173.google.com (HELO mail-qk0-f173.google.com) (209.85.220.173) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 17:06:33 -0000 Received: by qku63 with SMTP id 63so52423654qku.3 for ; Sun, 26 Apr 2015 10:06:32 -0700 (PDT) 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=QfQOR4fhwIilB5OpDnGoLCvdDjXLm11f/f5SldgZwLc=; b=h9mBPjgEbVyUhjjNwYKIwZfArDyzeOEdYG3SPRGo2+kgOG6NA9qKMCqnZTnHMiverA HrHcuN+Gt+1aG+K08hJrEr/0syzE2b4l9IyNRSKQGqoB9Ipt5/tOPiUtpuSBU6rcMULB 6dKoFcz/acsX+h+uyDI4r/ur/SoRMSjz475Yxx3MR1Qosiw4HjBfjpmq3c3XSjaoNfxi gYDMhlf5KIkcCbExMELRQNNM5PeE5+vZHZw6P1dEATjYZHSj6AINKCd2inKHul67OrzP sC1FzfADzNMLe8gx/3LjIbiWNuVtW4TZPQiA6D6LUCVxqcNlghqLM3ghFn15B+ZzQaW8 qr0w== MIME-Version: 1.0 X-Received: by 10.140.150.73 with SMTP id 70mr5530060qhw.10.1430067992826; Sun, 26 Apr 2015 10:06:32 -0700 (PDT) Received: by 10.229.250.2 with HTTP; Sun, 26 Apr 2015 10:06:32 -0700 (PDT) Date: Sun, 26 Apr 2015 13:06:32 -0400 Message-ID: From: Trevor Smith To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Cohttp and Higher Level Client 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="===============8639821061464848813==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8639821061464848813== Content-Type: multipart/alternative; boundary=001a1135531ab79b320514a3a6b8 --001a1135531ab79b320514a3a6b8 Content-Type: text/plain; charset=UTF-8 Hi all, tl;dr I would like to create a more feature-ful and higher level http client library. Should this go into cohttp or be a separate library? I would suggest it is a separate library. I would like to create a higher level http client to work with Async. I would excited to have this support LWT as well if others wanted to do that work. My personal needs at the moment are connection pooling, more sugar for ease of use (think ease of use of Python's Requests http://docs.python-requests.org/en/latest/), much more extensible (think http://www.intridea.com/blog/2012/3/12/faraday-one-http-client-to-rule-them-all). There's other things that one wants in a client library: dealing appropriately with cache headers, cookies and redirect handling that would need to be added at some point. It seems that Cohttp's current interface is low level, and that there's already been discussion suggesting that the complexity of implementing a http client should be part of another library ( https://github.com/mirage/ocaml-cohttp/issues/76). I would suggest that I begin work on this new library because it will be quicker to get the details ironed out without taking up the current maintainers time. I would see this library's relationship to Cohttp similar to https://github.com/rgrinberg/opium. There will need to be multiple changes to the current Cohttp Async client to support something like this, but I would try and keep those minimal, with the idea being that Cohttp stays the bedrock of http implementations for both client and servers. If at some point, it made sense to merge the efforts I'd be open to that. Also if the current maintainers feel strongly that this work should all go into Cohttp I am happy to contribute it there. Eager to hear your thoughts. Thanks. Trevor --001a1135531ab79b320514a3a6b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

tl;dr I would like to create a = more feature-ful and higher level http client library. Should this go into = cohttp or be a separate library? I would suggest it is a separate library.<= /div>

I would like to create a higher level http client = to work with Async. I would excited to have this support LWT as well if oth= ers wanted to do that work. My personal needs at the moment are connection = pooling, more sugar for ease of use (think ease of use of Python's Requ= ests http://docs.pyt= hon-requests.org/en/latest/), much more extensible (think=C2=A0http://www.intridea.com/blog/2012/3/12/faraday-one-http-client-to= -rule-them-all). There's other things that one wants in a client li= brary: dealing appropriately with cache headers, cookies and redirect handl= ing that would need to be added at some point.

It = seems that Cohttp's current interface is low level, and that there'= s already been discussion suggesting that the complexity of implementing a = http client should be part of another library (https://github.com/mirage/ocaml-cohttp/iss= ues/76).

I would suggest that I begin work on = this new library because it will be quicker to get the details ironed out w= ithout taking up the current maintainers time. I would see this library'= ;s relationship to Cohttp similar to https://github.com/rgrinberg/opium.

T= here will need to be multiple changes to the current Cohttp Async client to= support something like this, but I would try and keep those minimal, with = the idea being that Cohttp stays the bedrock of http implementations for bo= th client and servers. If at some point, it made sense to merge the efforts= I'd be open to that. Also if the current maintainers feel strongly tha= t this work should all go into Cohttp I am happy to contribute it there.

Eager to hear your thoughts. Thanks.

<= /div>
Trevor
--001a1135531ab79b320514a3a6b8-- --===============8639821061464848813== 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 --===============8639821061464848813==-- From mirageos-devel-bounces@lists.xenproject.org Sun Apr 26 17:54:08 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 17:54: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 1YmQkn-0007qy-IP; Sun, 26 Apr 2015 17:54:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmQkl-0007qt-TV for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 17:54:04 +0000 Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id B2/CF-24632-B362D355; Sun, 26 Apr 2015 17:54:03 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1430070842!19992311!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12588 invoked from network); 26 Apr 2015 17:54:02 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 17:54:02 -0000 Received: by wgin8 with SMTP id n8so94981808wgi.0 for ; Sun, 26 Apr 2015 10:54:02 -0700 (PDT) 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=fHUtLJmBIHEv8ptnI4LNxisZ8Os7/kucDSHXjWHREog=; b=hy22Pgq19gZqN2ocgZ+4Du6rtxK3HI+N4trpK5Jan1VV+cXK0rA7F8IptqeAe5ctLb e5NZAwaAeTKFvd50htu09/l17H+eaiiFv//zLqKXkvkfWDjwH5WcgargkhZswSD+25FV Yp3VwTcdfLZxqO4zNQTn74b5xZafOuznCwiKbCE8Tm4Oo/ybhsOdK+xEGuAtIP1E9wFF vctUhnKin8nEGVBD8I8BAMEauPRvRkPcoxv9hDqfxf4r0Ov/Pqi81sYHtBktJ6tDQohz 9KaDtxQ2cwvib352XOTwoEQJgtGnvQbby+pWY8j/Svz+JSlNgG7Kd/wMHykh/BDll/DK p/jA== X-Received: by 10.194.161.138 with SMTP id xs10mr15922528wjb.37.1430070841883; Sun, 26 Apr 2015 10:54:01 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id l1sm8171419wiy.20.2015.04.26.10.54.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Apr 2015 10:54:00 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 26 Apr 2015 18:53:59 +0100 Message-Id: <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2098) Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 25 Apr 2015, at 10:46, Thomas Leonard wrote: > > On 24 April 2015 at 15:47, Thomas Gazagnaire wrote: >> I've just merged the new watch API into the master branch of Irmin and I've updated the online docs. >> >> Feedback is welcome, the new functions are described on the related pull request [1]. > > Some more documentation would be useful. Currently, I see: > > val watch_head: t -> ?init:head -> (head diff -> unit Lwt.t) -> > (unit -> unit Lwt.t) Lwt.t > (** [watch_tag t f] calls [f] every time the contents of [t]'s tag is > updated. Do nothing if [t] is not persistent. Return a clean-up > function to remove the watch handler. > > "Do nothing if [t] is not persistent" This bit can be improved actually... > {b Note:} even [f] might skip some head updates, it will never > be called concurrently: all consecutive calls to [f] are done in > sequence, so we ensure that the previous one ended before > calling the next one. *) > > What does the "init" argument do? Will the callback be called > immediately with the current value if it's not given? What's the > recommended race-free way to start watching a branch? The init argument initialise the initial value kept by the watcher. If set to None, you'll have a `Added x` as first diff value, if not you'll have an `Updated (x,y)` where `x` is your initial value and `y` the new head. So you should first read the current head, then call watch_head with that head as init. > Currently (with the old API) I do: > > let watch_tags = I.watch_head (store "Watch branch") in > I.head (store "Get latest commit") >>= ... initial head ... > let head_id = ref (Some initial_head_id) in > async (fun () -> > watch_tags |> Lwt_stream.iter_s (function > ... > I.head (store "Get latest commit") >>= fun new_head_id -> > if new_head_id <> !head_id then ( > head_id := new_head_id > ) > ) > ) > > Here, I'm assuming that any change made after I.watch_head returns > will result in the callback being called. If the head has changed by > the time the initial I.head thread returns then the callback might get > called unnecessarily, but that's OK. > > How should this be done with the new API? I'm guessing something like: > > 1. Read the current head into a ref. > 2. Call I.watch_head with a callback to update the ref. > 3. Read the current head again in case it updated between (1) and (2). Not sure why you need 3. I guess you need it if you want to be sure that the head hasn't changed between the time the callback has been prepared (ie. to fetch the current head) and then called by Irmin - but if it is the case, the callback will be called again with the new head just after that. It is not possible to protect the callback completely though, as you have an other thread/process which can modify the store behind your back: in that case Irmin will detect the change (more or less quickly) and call the callback again with `Update (x,y)` where x is the previous head sent to the callback and y the new store's head. I'll improve the doc and give some examples though. 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 Sun Apr 26 17:54:08 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 17:54: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 1YmQkn-0007qy-IP; Sun, 26 Apr 2015 17:54:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmQkl-0007qt-TV for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 17:54:04 +0000 Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id B2/CF-24632-B362D355; Sun, 26 Apr 2015 17:54:03 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1430070842!19992311!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12588 invoked from network); 26 Apr 2015 17:54:02 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 17:54:02 -0000 Received: by wgin8 with SMTP id n8so94981808wgi.0 for ; Sun, 26 Apr 2015 10:54:02 -0700 (PDT) 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=fHUtLJmBIHEv8ptnI4LNxisZ8Os7/kucDSHXjWHREog=; b=hy22Pgq19gZqN2ocgZ+4Du6rtxK3HI+N4trpK5Jan1VV+cXK0rA7F8IptqeAe5ctLb e5NZAwaAeTKFvd50htu09/l17H+eaiiFv//zLqKXkvkfWDjwH5WcgargkhZswSD+25FV Yp3VwTcdfLZxqO4zNQTn74b5xZafOuznCwiKbCE8Tm4Oo/ybhsOdK+xEGuAtIP1E9wFF vctUhnKin8nEGVBD8I8BAMEauPRvRkPcoxv9hDqfxf4r0Ov/Pqi81sYHtBktJ6tDQohz 9KaDtxQ2cwvib352XOTwoEQJgtGnvQbby+pWY8j/Svz+JSlNgG7Kd/wMHykh/BDll/DK p/jA== X-Received: by 10.194.161.138 with SMTP id xs10mr15922528wjb.37.1430070841883; Sun, 26 Apr 2015 10:54:01 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id l1sm8171419wiy.20.2015.04.26.10.54.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Apr 2015 10:54:00 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 26 Apr 2015 18:53:59 +0100 Message-Id: <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2098) Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 25 Apr 2015, at 10:46, Thomas Leonard wrote: > > On 24 April 2015 at 15:47, Thomas Gazagnaire wrote: >> I've just merged the new watch API into the master branch of Irmin and I've updated the online docs. >> >> Feedback is welcome, the new functions are described on the related pull request [1]. > > Some more documentation would be useful. Currently, I see: > > val watch_head: t -> ?init:head -> (head diff -> unit Lwt.t) -> > (unit -> unit Lwt.t) Lwt.t > (** [watch_tag t f] calls [f] every time the contents of [t]'s tag is > updated. Do nothing if [t] is not persistent. Return a clean-up > function to remove the watch handler. > > "Do nothing if [t] is not persistent" This bit can be improved actually... > {b Note:} even [f] might skip some head updates, it will never > be called concurrently: all consecutive calls to [f] are done in > sequence, so we ensure that the previous one ended before > calling the next one. *) > > What does the "init" argument do? Will the callback be called > immediately with the current value if it's not given? What's the > recommended race-free way to start watching a branch? The init argument initialise the initial value kept by the watcher. If set to None, you'll have a `Added x` as first diff value, if not you'll have an `Updated (x,y)` where `x` is your initial value and `y` the new head. So you should first read the current head, then call watch_head with that head as init. > Currently (with the old API) I do: > > let watch_tags = I.watch_head (store "Watch branch") in > I.head (store "Get latest commit") >>= ... initial head ... > let head_id = ref (Some initial_head_id) in > async (fun () -> > watch_tags |> Lwt_stream.iter_s (function > ... > I.head (store "Get latest commit") >>= fun new_head_id -> > if new_head_id <> !head_id then ( > head_id := new_head_id > ) > ) > ) > > Here, I'm assuming that any change made after I.watch_head returns > will result in the callback being called. If the head has changed by > the time the initial I.head thread returns then the callback might get > called unnecessarily, but that's OK. > > How should this be done with the new API? I'm guessing something like: > > 1. Read the current head into a ref. > 2. Call I.watch_head with a callback to update the ref. > 3. Read the current head again in case it updated between (1) and (2). Not sure why you need 3. I guess you need it if you want to be sure that the head hasn't changed between the time the callback has been prepared (ie. to fetch the current head) and then called by Irmin - but if it is the case, the callback will be called again with the new head just after that. It is not possible to protect the callback completely though, as you have an other thread/process which can modify the store behind your back: in that case Irmin will detect the change (more or less quickly) and call the callback again with `Update (x,y)` where x is the previous head sent to the callback and y the new store's head. I'll improve the doc and give some examples though. 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 Sun Apr 26 18:15:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 18:15:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmR5B-0008EX-2U; Sun, 26 Apr 2015 18:15:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmR58-0008EP-VP for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 18:15:07 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id 9E/30-14044-A2B2D355; Sun, 26 Apr 2015 18:15:06 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1430072101!18701968!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14386 invoked from network); 26 Apr 2015 18:15:05 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 18:15:05 -0000 Received: by lagv1 with SMTP id v1so65601862lag.3 for ; Sun, 26 Apr 2015 11:15:01 -0700 (PDT) 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:content-transfer-encoding; bh=9GeTluHh5rlZFtiDI3BW0/ytAgeOKcvl/M3SDKMjR1k=; b=HuDQh8cT0RuDQkeuewLqBloLiIqQoEjzgSOYVPONjWkbyjTwnKbhFzqcF9KcVYvAyl B9J0tZezox5pKpvKch/zDGAiI0q2boDdJbp+svfdjYk7jXq7s/mx8VW0ZO40Anx9Kikt w2JKqwpIFAyxVOzF6yoWqeor1KTT7mkiM40+FFuqf59YzbnNLy7dUBSCdvYHexF9R4q3 2NBbmwkpz93Oa5cEIXR5TNeDeJ6Y9jaI8lo2udON3cud0WaoDZ4cDOvVFa90AlDj2iis +npjrjadULVEKPX+H7T3zC17kZamP945No6NoPAc4cTutY1qxo36JCJiNDa3+gOLUEhN BIDA== MIME-Version: 1.0 X-Received: by 10.152.19.132 with SMTP id f4mr6880524lae.115.1430072100953; Sun, 26 Apr 2015 11:15:00 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sun, 26 Apr 2015 11:15:00 -0700 (PDT) In-Reply-To: <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> Date: Sun, 26 Apr 2015 19:15:00 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 26 April 2015 at 18:53, Thomas Gazagnaire wrote: > >> On 25 Apr 2015, at 10:46, Thomas Leonard wrote: >> >> On 24 April 2015 at 15:47, Thomas Gazagnaire wrote: >>> I've just merged the new watch API into the master branch of Irmin and I've updated the online docs. >>> >>> Feedback is welcome, the new functions are described on the related pull request [1]. >> >> Some more documentation would be useful. Currently, I see: >> >> val watch_head: t -> ?init:head -> (head diff -> unit Lwt.t) -> >> (unit -> unit Lwt.t) Lwt.t >> (** [watch_tag t f] calls [f] every time the contents of [t]'s tag is >> updated. Do nothing if [t] is not persistent. Return a clean-up >> function to remove the watch handler. >> > >> "Do nothing if [t] is not persistent" > This bit can be improved actually... > > >> {b Note:} even [f] might skip some head updates, it will never >> be called concurrently: all consecutive calls to [f] are done in >> sequence, so we ensure that the previous one ended before >> calling the next one. *) >> >> What does the "init" argument do? Will the callback be called >> immediately with the current value if it's not given? What's the >> recommended race-free way to start watching a branch? > > The init argument initialise the initial value kept by the watcher. If set to None, you'll have a `Added x` as first diff value, if not you'll have an `Updated (x,y)` where `x` is your initial value and `y` the new head. So you should first read the current head, then call watch_head with that head as init. > >> Currently (with the old API) I do: >> >> let watch_tags = I.watch_head (store "Watch branch") in >> I.head (store "Get latest commit") >>= ... initial head ... >> let head_id = ref (Some initial_head_id) in >> async (fun () -> >> watch_tags |> Lwt_stream.iter_s (function >> ... >> I.head (store "Get latest commit") >>= fun new_head_id -> >> if new_head_id <> !head_id then ( >> head_id := new_head_id >> ) >> ) >> ) >> >> Here, I'm assuming that any change made after I.watch_head returns >> will result in the callback being called. If the head has changed by >> the time the initial I.head thread returns then the callback might get >> called unnecessarily, but that's OK. >> >> How should this be done with the new API? I'm guessing something like: >> >> 1. Read the current head into a ref. >> 2. Call I.watch_head with a callback to update the ref. >> 3. Read the current head again in case it updated between (1) and (2). > > Not sure why you need 3. I guess you need it if you want to be sure that the head hasn't changed between the time the callback has been prepared (ie. to fetch the current head) and then called by Irmin - but if it is the case, the callback will be called again with the new head just after that. It is not possible to protect the callback completely though, as you have an other thread/process which can modify the store behind your back: in that case Irmin will detect the change (more or less quickly) and call the callback again with `Update (x,y)` where x is the previous head sent to the callback and y the new store's head. The situation I'm not sure about is: 1. I read the head (at c1). 2. (the head is updated to c2 by another tab) 3. I call I.watch_head to get notifications. The change happened before I asked Irmin to watch the head, so I assume it won't notify me (unless it always starts with a notification even when there is no change, in which case this should be documented). > I'll improve the doc and give some examples though. > > Thomas Thanks, -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 26 18:15:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 18:15:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmR5B-0008EX-2U; Sun, 26 Apr 2015 18:15:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmR58-0008EP-VP for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 18:15:07 +0000 Received: from [85.158.139.211] by server-15.bemta-5.messagelabs.com id 9E/30-14044-A2B2D355; Sun, 26 Apr 2015 18:15:06 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1430072101!18701968!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14386 invoked from network); 26 Apr 2015 18:15:05 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 18:15:05 -0000 Received: by lagv1 with SMTP id v1so65601862lag.3 for ; Sun, 26 Apr 2015 11:15:01 -0700 (PDT) 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:content-transfer-encoding; bh=9GeTluHh5rlZFtiDI3BW0/ytAgeOKcvl/M3SDKMjR1k=; b=HuDQh8cT0RuDQkeuewLqBloLiIqQoEjzgSOYVPONjWkbyjTwnKbhFzqcF9KcVYvAyl B9J0tZezox5pKpvKch/zDGAiI0q2boDdJbp+svfdjYk7jXq7s/mx8VW0ZO40Anx9Kikt w2JKqwpIFAyxVOzF6yoWqeor1KTT7mkiM40+FFuqf59YzbnNLy7dUBSCdvYHexF9R4q3 2NBbmwkpz93Oa5cEIXR5TNeDeJ6Y9jaI8lo2udON3cud0WaoDZ4cDOvVFa90AlDj2iis +npjrjadULVEKPX+H7T3zC17kZamP945No6NoPAc4cTutY1qxo36JCJiNDa3+gOLUEhN BIDA== MIME-Version: 1.0 X-Received: by 10.152.19.132 with SMTP id f4mr6880524lae.115.1430072100953; Sun, 26 Apr 2015 11:15:00 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sun, 26 Apr 2015 11:15:00 -0700 (PDT) In-Reply-To: <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> Date: Sun, 26 Apr 2015 19:15:00 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 26 April 2015 at 18:53, Thomas Gazagnaire wrote: > >> On 25 Apr 2015, at 10:46, Thomas Leonard wrote: >> >> On 24 April 2015 at 15:47, Thomas Gazagnaire wrote: >>> I've just merged the new watch API into the master branch of Irmin and I've updated the online docs. >>> >>> Feedback is welcome, the new functions are described on the related pull request [1]. >> >> Some more documentation would be useful. Currently, I see: >> >> val watch_head: t -> ?init:head -> (head diff -> unit Lwt.t) -> >> (unit -> unit Lwt.t) Lwt.t >> (** [watch_tag t f] calls [f] every time the contents of [t]'s tag is >> updated. Do nothing if [t] is not persistent. Return a clean-up >> function to remove the watch handler. >> > >> "Do nothing if [t] is not persistent" > This bit can be improved actually... > > >> {b Note:} even [f] might skip some head updates, it will never >> be called concurrently: all consecutive calls to [f] are done in >> sequence, so we ensure that the previous one ended before >> calling the next one. *) >> >> What does the "init" argument do? Will the callback be called >> immediately with the current value if it's not given? What's the >> recommended race-free way to start watching a branch? > > The init argument initialise the initial value kept by the watcher. If set to None, you'll have a `Added x` as first diff value, if not you'll have an `Updated (x,y)` where `x` is your initial value and `y` the new head. So you should first read the current head, then call watch_head with that head as init. > >> Currently (with the old API) I do: >> >> let watch_tags = I.watch_head (store "Watch branch") in >> I.head (store "Get latest commit") >>= ... initial head ... >> let head_id = ref (Some initial_head_id) in >> async (fun () -> >> watch_tags |> Lwt_stream.iter_s (function >> ... >> I.head (store "Get latest commit") >>= fun new_head_id -> >> if new_head_id <> !head_id then ( >> head_id := new_head_id >> ) >> ) >> ) >> >> Here, I'm assuming that any change made after I.watch_head returns >> will result in the callback being called. If the head has changed by >> the time the initial I.head thread returns then the callback might get >> called unnecessarily, but that's OK. >> >> How should this be done with the new API? I'm guessing something like: >> >> 1. Read the current head into a ref. >> 2. Call I.watch_head with a callback to update the ref. >> 3. Read the current head again in case it updated between (1) and (2). > > Not sure why you need 3. I guess you need it if you want to be sure that the head hasn't changed between the time the callback has been prepared (ie. to fetch the current head) and then called by Irmin - but if it is the case, the callback will be called again with the new head just after that. It is not possible to protect the callback completely though, as you have an other thread/process which can modify the store behind your back: in that case Irmin will detect the change (more or less quickly) and call the callback again with `Update (x,y)` where x is the previous head sent to the callback and y the new store's head. The situation I'm not sure about is: 1. I read the head (at c1). 2. (the head is updated to c2 by another tab) 3. I call I.watch_head to get notifications. The change happened before I asked Irmin to watch the head, so I assume it won't notify me (unless it always starts with a notification even when there is no change, in which case this should be documented). > I'll improve the doc and give some examples though. > > Thomas Thanks, -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 26 18:46:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 18:46: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 1YmRZc-0000Gj-AR; Sun, 26 Apr 2015 18:46:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmRZb-0000Ge-Oz for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 18:46:35 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id 92/CD-25404-A823D355; Sun, 26 Apr 2015 18:46:34 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1430073994!18706282!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31948 invoked from network); 26 Apr 2015 18:46:34 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 18:46:34 -0000 Received: by wiun10 with SMTP id n10so68256963wiu.1 for ; Sun, 26 Apr 2015 11:46:33 -0700 (PDT) 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=fZdQ4hkhHYMASXaHccyUJNpXuMHB8vvjtlCXDUZLrj0=; b=sUdFFdKJQJWPONp3Nwd4loqlPvpXFeDTK2yXaW66XYaYpFg+gUXzeIaaG5yqKqi1al IWbotCeRQvZK4doVDMzdldkPGG0l50Qinp5vx+dtZHwNeEBQg/YETt5vojpVyarJC7w/ iIJBzY4I7ndt8Qu9cp19YeZJ0idSWCiY86cGjqyHIfvIwMFTuojYZ2WD1xg+k3lOdt4d k3tGzHtdLgd0DykP1M3BN6aHTobBk33dCQ9uaec+YWJXBVp6SvShy0OIxuvs5xdvDcWc tpNWHJrQP640/AzhoiPYna8m4j8fAt/Bf9EZK8sXhOLsnyqKhntpOAuUtTntsftUjAQx +Tew== X-Received: by 10.194.238.161 with SMTP id vl1mr15650580wjc.144.1430073993803; Sun, 26 Apr 2015 11:46:33 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id i6sm26141883wjf.29.2015.04.26.11.46.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Apr 2015 11:46:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 26 Apr 2015 19:46:32 +0100 Message-Id: References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2098) Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 > The situation I'm not sure about is: > > 1. I read the head (at c1). > 2. (the head is updated to c2 by another tab) > 3. I call I.watch_head to get notifications. > > The change happened before I asked Irmin to watch the head, so I > assume it won't notify me (unless it always starts with a notification > even when there is no change, in which case this should be > documented). If you call 3. with init=(head c1) then you'll get an immediate notification with `Updated (head c1, head c2)` 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 Sun Apr 26 18:46:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 18:46: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 1YmRZc-0000Gj-AR; Sun, 26 Apr 2015 18:46:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmRZb-0000Ge-Oz for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 18:46:35 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id 92/CD-25404-A823D355; Sun, 26 Apr 2015 18:46:34 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1430073994!18706282!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31948 invoked from network); 26 Apr 2015 18:46:34 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 18:46:34 -0000 Received: by wiun10 with SMTP id n10so68256963wiu.1 for ; Sun, 26 Apr 2015 11:46:33 -0700 (PDT) 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=fZdQ4hkhHYMASXaHccyUJNpXuMHB8vvjtlCXDUZLrj0=; b=sUdFFdKJQJWPONp3Nwd4loqlPvpXFeDTK2yXaW66XYaYpFg+gUXzeIaaG5yqKqi1al IWbotCeRQvZK4doVDMzdldkPGG0l50Qinp5vx+dtZHwNeEBQg/YETt5vojpVyarJC7w/ iIJBzY4I7ndt8Qu9cp19YeZJ0idSWCiY86cGjqyHIfvIwMFTuojYZ2WD1xg+k3lOdt4d k3tGzHtdLgd0DykP1M3BN6aHTobBk33dCQ9uaec+YWJXBVp6SvShy0OIxuvs5xdvDcWc tpNWHJrQP640/AzhoiPYna8m4j8fAt/Bf9EZK8sXhOLsnyqKhntpOAuUtTntsftUjAQx +Tew== X-Received: by 10.194.238.161 with SMTP id vl1mr15650580wjc.144.1430073993803; Sun, 26 Apr 2015 11:46:33 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id i6sm26141883wjf.29.2015.04.26.11.46.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Apr 2015 11:46:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 26 Apr 2015 19:46:32 +0100 Message-Id: References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2098) Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 > The situation I'm not sure about is: > > 1. I read the head (at c1). > 2. (the head is updated to c2 by another tab) > 3. I call I.watch_head to get notifications. > > The change happened before I asked Irmin to watch the head, so I > assume it won't notify me (unless it always starts with a notification > even when there is no change, in which case this should be > documented). If you call 3. with init=(head c1) then you'll get an immediate notification with `Updated (head c1, head c2)` 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 Sun Apr 26 19:35:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 19:35:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmSL6-000141-QZ; Sun, 26 Apr 2015 19:35:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmSL5-00013w-TU for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 19:35:40 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 92/4F-27592-B0E3D355; Sun, 26 Apr 2015 19:35:39 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1430076937!12260698!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30890 invoked from network); 26 Apr 2015 19:35:38 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 19:35:38 -0000 Received: by lagv1 with SMTP id v1so66304769lag.3 for ; Sun, 26 Apr 2015 12:35:37 -0700 (PDT) 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=pMawf1gwtX1z7RglDHSbOZ5+7BzRui3LqGt/2CC64ck=; b=CMGOyEgseEppHQ92/7OQkM8rPsPJbVQBCw32a60bIBU1dHXisutcD2AvJq4UK+Dn+N TjjWPdehRW78jjYeQOWSt5iUqiyRwJfIW+6eaWHWxRZ3XwibMRyOQBiFz2z97STcmyCs uQ604kKIgrmkIngMk7MUnT8C+lkYhUMGG3J4Xg9sYBLFvfn6RVkDqUdtY5rI5Db2jaxi 6c6Wf2LdYOMf4t0inqsurAkFPOpMaUf5zaAqfCsnRyEB51+5fvJ8xuhy0DFbuWCxZYCk XNNHSziU6sfSdND+YDVmskw4iKNC4/Nq7puPM3iMThCUPIkQ/PA0Avq0jZWeUG8igOTU UiMA== MIME-Version: 1.0 X-Received: by 10.152.19.132 with SMTP id f4mr7082240lae.115.1430076937554; Sun, 26 Apr 2015 12:35:37 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sun, 26 Apr 2015 12:35:37 -0700 (PDT) In-Reply-To: References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> Date: Sun, 26 Apr 2015 20:35:37 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 26 April 2015 at 19:46, Thomas Gazagnaire wrote: >> The situation I'm not sure about is: >> >> 1. I read the head (at c1). >> 2. (the head is updated to c2 by another tab) >> 3. I call I.watch_head to get notifications. >> >> The change happened before I asked Irmin to watch the head, so I >> assume it won't notify me (unless it always starts with a notification >> even when there is no change, in which case this should be >> documented). > > If you call 3. with init=(head c1) then you'll get an immediate notification with `Updated (head c1, head c2)` OK, that's perfect then! Thanks, -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 26 19:35:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Apr 2015 19:35:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmSL6-000141-QZ; Sun, 26 Apr 2015 19:35:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmSL5-00013w-TU for mirageos-devel@lists.xenproject.org; Sun, 26 Apr 2015 19:35:40 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id 92/4F-27592-B0E3D355; Sun, 26 Apr 2015 19:35:39 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1430076937!12260698!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30890 invoked from network); 26 Apr 2015 19:35:38 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2015 19:35:38 -0000 Received: by lagv1 with SMTP id v1so66304769lag.3 for ; Sun, 26 Apr 2015 12:35:37 -0700 (PDT) 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=pMawf1gwtX1z7RglDHSbOZ5+7BzRui3LqGt/2CC64ck=; b=CMGOyEgseEppHQ92/7OQkM8rPsPJbVQBCw32a60bIBU1dHXisutcD2AvJq4UK+Dn+N TjjWPdehRW78jjYeQOWSt5iUqiyRwJfIW+6eaWHWxRZ3XwibMRyOQBiFz2z97STcmyCs uQ604kKIgrmkIngMk7MUnT8C+lkYhUMGG3J4Xg9sYBLFvfn6RVkDqUdtY5rI5Db2jaxi 6c6Wf2LdYOMf4t0inqsurAkFPOpMaUf5zaAqfCsnRyEB51+5fvJ8xuhy0DFbuWCxZYCk XNNHSziU6sfSdND+YDVmskw4iKNC4/Nq7puPM3iMThCUPIkQ/PA0Avq0jZWeUG8igOTU UiMA== MIME-Version: 1.0 X-Received: by 10.152.19.132 with SMTP id f4mr7082240lae.115.1430076937554; Sun, 26 Apr 2015 12:35:37 -0700 (PDT) Received: by 10.25.207.148 with HTTP; Sun, 26 Apr 2015 12:35:37 -0700 (PDT) In-Reply-To: References: <42AE682F-37A7-4BBD-B1C5-1534B68EBB17@gazagnaire.org> <8A661495-6C5D-49B7-AD3B-2F2CB82A0B9D@gazagnaire.org> Date: Sun, 26 Apr 2015 20:35:37 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: Mirageos-devel Subject: Re: [MirageOS-devel] Irmin watch API 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 26 April 2015 at 19:46, Thomas Gazagnaire wrote: >> The situation I'm not sure about is: >> >> 1. I read the head (at c1). >> 2. (the head is updated to c2 by another tab) >> 3. I call I.watch_head to get notifications. >> >> The change happened before I asked Irmin to watch the head, so I >> assume it won't notify me (unless it always starts with a notification >> even when there is no change, in which case this should be >> documented). > > If you call 3. with init=(head c1) then you'll get an immediate notification with `Updated (head c1, head c2)` OK, that's perfect then! Thanks, -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ 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 Apr 27 03:21:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Apr 2015 03:21: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 1YmZbt-000554-Sj; Mon, 27 Apr 2015 03:21:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YmZbs-00054z-EZ for mirageos-devel@lists.xenproject.org; Mon, 27 Apr 2015 03:21:28 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 0D/DB-29893-73BAD355; Mon, 27 Apr 2015 03:21:27 +0000 X-Env-Sender: rudi.grinberg@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1430104884!6916953!1 X-Originating-IP: [209.85.223.180] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31406 invoked from network); 27 Apr 2015 03:21:25 -0000 Received: from mail-ie0-f180.google.com (HELO mail-ie0-f180.google.com) (209.85.223.180) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2015 03:21:25 -0000 Received: by iebrs15 with SMTP id rs15so117672472ieb.3 for ; Sun, 26 Apr 2015 20:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type; bh=la4wxlA4PIMvQW0czXaYIZzpimqQYs8KAnU8DqK3hy0=; b=Z6r0TjtYzJ0gwK4maSLgoYDRugAP5Y95BlY88EcLu+/4jhisfrq5zceDAaTmUWN8cU bDv3alFK9fMkqFk4jB1iKJkkihbmeyWuFTIz8hkAiQee8X0wFZmHWCfCn/6L2iW+CjyV isLyEvdtffGW3bPSShrvhQWey9fNZBJfd6hYY62bj1rGDiDxiPgruAGYdzHoNnHgqVzF ZI9Ac1WE2E4TXnAoGcnE2SCfP6853x1HLzFyOx4bAYmvlV2UHJGpF6VTIp/Nnzr11y+p PhiGgnk5RdvHCf8I7T2b8smLDSJbvIlso4rSPKWJ028oDghChcfMLsUgF4dzK0dunP7K IDdw== X-Received: by 10.50.43.136 with SMTP id w8mr10747766igl.26.1430104884250; Sun, 26 Apr 2015 20:21:24 -0700 (PDT) Received: from Rudis-MacBook-Pro.local ([66.49.180.208]) by mx.google.com with ESMTPSA id l3sm4407163ige.21.2015.04.26.20.21.23 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Apr 2015 20:21:23 -0700 (PDT) Date: Sun, 26 Apr 2015 23:26:12 -0400 From: Rudi Grinberg To: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" , Trevor Smith Message-ID: In-Reply-To: References: X-Mailer: Airmail Beta (301) MIME-Version: 1.0 Subject: Re: [MirageOS-devel] Cohttp and Higher Level Client 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="===============7478894599344603308==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7478894599344603308== Content-Type: multipart/alternative; boundary="553dac54_7f53d9dd_1092e" --553dac54_7f53d9dd_1092e Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Just to chime in, the suggestion to create a client that lives outside of= cohttp is also supported by me.=C2=A0 I think the design space for http clients is large enough to support many= different libraries. I wouldn=E2=80=99t want to use cohttp=E2=80=99s pos= ition to prevent people from experimenting. Aside from that, there=E2=80=99= s also the more practical reason that the current maintainers (including = me) seem to have a large enough backlog in cohttp without adding designin= g/implementing/testing an http client to our list. Rudi. On April 26, 2015 at 1:07:14 PM, Trevor Smith (trevorsummerssmith=40gmail= .com) wrote: Hi all, tl;dr I would like to create a more feature-ful and higher level http cli= ent library. Should this go into cohttp or be a separate library=3F I wou= ld suggest it is a separate library. I would like to create a higher level http client to work with Async. I w= ould excited to have this support LWT as well if others wanted to do that= work. My personal needs at the moment are connection pooling, more sugar= for ease of use (think ease of use of Python's Requests http://docs.pyth= on-requests.org/en/latest/), much more extensible (think=C2=A0http://www.= intridea.com/blog/2012/3/12/faraday-one-http-client-to-rule-them-all). Th= ere's other things that one wants in a client library: dealing appropriat= ely with cache headers, cookies and redirect handling that would need to = be added at some point. It seems that Cohttp's current interface is low level, and that there's a= lready been discussion suggesting that the complexity of implementing a h= ttp client should be part of another library (https://github.com/mirage/o= caml-cohttp/issues/76). I would suggest that I begin work on this new library because it will be = quicker to get the details ironed out without taking up the current maint= ainers time. I would see this library's relationship to Cohttp similar to= https://github.com/rgrinberg/opium. There will need to be multiple changes to the current Cohttp Async client= to support something like this, but I would try and keep those minimal, = with the idea being that Cohttp stays the bedrock of http implementations= for both client and servers. If at some point, it made sense to merge th= e efforts I'd be open to that. Also if the current maintainers feel stron= gly that this work should all go into Cohttp I am happy to contribute it = there. Eager to hear your thoughts. Thanks. Trevor =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F =20 MirageOS-devel mailing list =20 MirageOS-devel=40lists.xenproject.org =20 http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel =20 --553dac54_7f53d9dd_1092e Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =0A=
I don't know if this is related=2C but I also got=2C just = a few hours ago=2C a similar error running mirage-mdns on xen 4.4.1=2C ubun= tu trusty=2C amd64:


sudo xl create -c mdns-resp-test.xl
[sudo= ] password for nick:
Parsing config from mdns-resp-test.xl
Xen Minim= al OS!
 =3B start_info: 000000000030d000(VA)
 =3B =3B&nbs= p=3B nr_pages: 0x10000
 =3B shared_inf: 0x9e733000(MA)
 =3B&n= bsp=3B =3B =3B pt_base: 0000000000310000(VA)
nr_pt_frames: 0x5 =3B =3B =3B mfn_list: 000000000028d000(VA)
 =3B = =3B mod_start: 0x0(VA)
 =3B =3B =3B =3B mod_len: 0
&n= bsp=3B =3B =3B =3B =3B =3B flags: 0x0
 =3B = =3B =3B cmd_line:
 =3B =3B =3B =3B =3B =3B = stack: 000000000026c2e0-000000000028c2e0
MM: Init
 =3B =3B&nb= sp=3B =3B =3B _text: 0000000000000000(VA)
 =3B =3B = =3B =3B _etext: 000000000013e07f(VA)
 =3B =3B _erodata: 0000= 00000017b000(VA)
 =3B =3B =3B =3B _edata: 0000000000232b= 60(VA)
stack start: 000000000026c2e0(VA)
 =3B =3B =3B&nbs= p=3B =3B =3B _end: 000000000028c2e0(VA)
 =3B start_pfn: 318<= br> =3B =3B =3B max_pfn: 10000
Mapping memory range 0x400000= - 0x10000000
setting 0000000000000000-000000000017b000 readonly
skip= ped 1000
MM: Initialise page allocator for 396000(396000)-10000000(10000= 000)
MM: done
Demand map pfns at 10001000-0000002010001000.
Initia= lising timer interface
Initialising console ... done.
gnttab_table ma= pped at 0000000010001000.
getenv(OCAMLRUNPARAM) ->=3B null
getenv(C= AMLRUNPARAM) ->=3B null
getenv(PATH) ->=3B null
Unsupported funct= ion lseek called in Mini-OS kernel
Unsupported function lseek called in = Mini-OS kernel
Unsupported function lseek called in Mini-OS kernel
ge= tenv(OCAMLRUNPARAM) ->=3B null
getenv(CAMLRUNPARAM) ->=3B null
ge= tenv(TMPDIR) ->=3B null
getenv(TEMP) ->=3B null
Netif: add resume= hook
Netif.connect tap0: could not find device
Fatal error: exceptio= n Failure("\n\nnet_tap0: device tap0 not found (available =3D [ =3B ])\= nIf using a tap device=2C is tun/tap enabled and have you permissions?\n\n"= )
Raised at file "src/core/lwt.ml"=2C line 788=2C characters 22-23
Ca= lled from file "lib/main.ml"=2C line 58=2C characters 10-20
Called from = file "main.ml"=2C line 85=2C characters 2-28
Mirage exiting with status = 2
Do_exit called!
base is 0x27ff20 caller is 0x1237b1
base is 0x23= 2530 caller is 0x0
base is 0x141783 caller is 0x5241570000000000
base= is 0x65676172696d Page fault at linear address 656761726975=2C rip 13d607= =2C regs 000000000027fe38=2C sp 27fee0=2C our_sp 000000000027fdf8=2C code 0=
RIP: e030:[<=3B000000000013d607>=3B]
RSP: e02b:000000000027fee0=  =3B EFLAGS: 00010006
RAX: 0000000000000017 RBX: 000065676172696d RC= X: 0000000000000743
RDX: 0000000000000743 RSI: 000000000027fd30 RDI: 000= 0000000000004
RBP: 000000000027ff20 R08: 0000000000000742 R09: 000000000= 0000020
R10: 0000000000000017 R11: 0000000000000000 R12: 000000000000000= 0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
b= ase is 0x27ff20 caller is 0x1237b1
base is 0x232530 caller is 0x0
bas= e is 0x141783 caller is 0x5241570000000000
base is 0x65676172696d Page f= ault in pagetable walk (access to invalid memory?).


=0A=
= --_73dfdf26-8b66-45a8-8bdd-5aacd0a8f36e_-- --===============0677013366819534089== 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 --===============0677013366819534089==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 14:47:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 14:47: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 1YnTH3-0003L9-Tg; Wed, 29 Apr 2015 14:47:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnTH2-0003L4-PL for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 14:47:41 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id 04/35-03711-B0FE0455; Wed, 29 Apr 2015 14:47:39 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1430318858!8537599!1 X-Originating-IP: [157.55.2.100] X-SpamReason: No, hits=1.5 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8378 invoked from network); 29 Apr 2015 14:47:38 -0000 Received: from dub004-omc4s25.hotmail.com (HELO DUB004-OMC4S25.hotmail.com) (157.55.2.100) by server-14.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 14:47:38 -0000 Received: from DUB128-W92 ([157.55.2.72]) by DUB004-OMC4S25.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 07:47:38 -0700 X-TMN: [pOsXnsyKBO0F48nZiVklp+A2IOXf5njt] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: Anil Madhavapeddy , Justin Cormack Date: Wed, 29 Apr 2015 14:47:37 +0000 Importance: Normal In-Reply-To: <1153A97D-9C94-4F8D-BBE8-A2E5434582A9@recoil.org> References: , <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org>, , <1153A97D-9C94-4F8D-BBE8-A2E5434582A9@recoil.org> MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 14:47:38.0262 (UTC) FILETIME=[6FDDDB60:01D0828B] Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============0677013366819534089==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0677013366819534089== Content-Type: multipart/alternative; boundary="_73dfdf26-8b66-45a8-8bdd-5aacd0a8f36e_" --_73dfdf26-8b66-45a8-8bdd-5aacd0a8f36e_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= I don't know if this is related=2C but I also got=2C just a few hours ago= =2C a similar error running mirage-mdns on xen 4.4.1=2C ubuntu trusty=2C am= d64: sudo xl create -c mdns-resp-test.xl [sudo] password for nick:=20 Parsing config from mdns-resp-test.xl Xen Minimal OS! start_info: 000000000030d000(VA) nr_pages: 0x10000 shared_inf: 0x9e733000(MA) pt_base: 0000000000310000(VA) nr_pt_frames: 0x5 mfn_list: 000000000028d000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line:=20 stack: 000000000026c2e0-000000000028c2e0 MM: Init _text: 0000000000000000(VA) _etext: 000000000013e07f(VA) _erodata: 000000000017b000(VA) _edata: 0000000000232b60(VA) stack start: 000000000026c2e0(VA) _end: 000000000028c2e0(VA) start_pfn: 318 max_pfn: 10000 Mapping memory range 0x400000 - 0x10000000 setting 0000000000000000-000000000017b000 readonly skipped 1000 MM: Initialise page allocator for 396000(396000)-10000000(10000000) MM: done Demand map pfns at 10001000-0000002010001000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0000000010001000. getenv(OCAMLRUNPARAM) -> null getenv(CAMLRUNPARAM) -> null getenv(PATH) -> null Unsupported function lseek called in Mini-OS kernel Unsupported function lseek called in Mini-OS kernel Unsupported function lseek called in Mini-OS kernel getenv(OCAMLRUNPARAM) -> null getenv(CAMLRUNPARAM) -> null getenv(TMPDIR) -> null getenv(TEMP) -> null Netif: add resume hook Netif.connect tap0: could not find device Fatal error: exception Failure("\n\nnet_tap0: device tap0 not found (availa= ble =3D [ ])\nIf using a tap device=2C is tun/tap enabled and have you per= missions?\n\n") Raised at file "src/core/lwt.ml"=2C line 788=2C characters 22-23 Called from file "lib/main.ml"=2C line 58=2C characters 10-20 Called from file "main.ml"=2C line 85=2C characters 2-28 Mirage exiting with status 2 Do_exit called! base is 0x27ff20 caller is 0x1237b1 base is 0x232530 caller is 0x0 base is 0x141783 caller is 0x5241570000000000 base is 0x65676172696d Page fault at linear address 656761726975=2C rip 13d= 607=2C regs 000000000027fe38=2C sp 27fee0=2C our_sp 000000000027fdf8=2C cod= e 0 RIP: e030:[<000000000013d607>]=20 RSP: e02b:000000000027fee0 EFLAGS: 00010006 RAX: 0000000000000017 RBX: 000065676172696d RCX: 0000000000000743 RDX: 0000000000000743 RSI: 000000000027fd30 RDI: 0000000000000004 RBP: 000000000027ff20 R08: 0000000000000742 R09: 0000000000000020 R10: 0000000000000017 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 base is 0x27ff20 caller is 0x1237b1 base is 0x232530 caller is 0x0 base is 0x141783 caller is 0x5241570000000000 base is 0x65676172696d Page fault in pagetable walk (access to invalid memo= ry?). =0A= = --_73dfdf26-8b66-45a8-8bdd-5aacd0a8f36e_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
=0A= =0A= =0A=
I don't know if this is related=2C but I also got=2C just = a few hours ago=2C a similar error running mirage-mdns on xen 4.4.1=2C ubun= tu trusty=2C amd64:


sudo xl create -c mdns-resp-test.xl
[sudo= ] password for nick:
Parsing config from mdns-resp-test.xl
Xen Minim= al OS!
 =3B start_info: 000000000030d000(VA)
 =3B =3B&nbs= p=3B nr_pages: 0x10000
 =3B shared_inf: 0x9e733000(MA)
 =3B&n= bsp=3B =3B =3B pt_base: 0000000000310000(VA)
nr_pt_frames: 0x5 =3B =3B =3B mfn_list: 000000000028d000(VA)
 =3B = =3B mod_start: 0x0(VA)
 =3B =3B =3B =3B mod_len: 0
&n= bsp=3B =3B =3B =3B =3B =3B flags: 0x0
 =3B = =3B =3B cmd_line:
 =3B =3B =3B =3B =3B =3B = stack: 000000000026c2e0-000000000028c2e0
MM: Init
 =3B =3B&nb= sp=3B =3B =3B _text: 0000000000000000(VA)
 =3B =3B = =3B =3B _etext: 000000000013e07f(VA)
 =3B =3B _erodata: 0000= 00000017b000(VA)
 =3B =3B =3B =3B _edata: 0000000000232b= 60(VA)
stack start: 000000000026c2e0(VA)
 =3B =3B =3B&nbs= p=3B =3B =3B _end: 000000000028c2e0(VA)
 =3B start_pfn: 318<= br> =3B =3B =3B max_pfn: 10000
Mapping memory range 0x400000= - 0x10000000
setting 0000000000000000-000000000017b000 readonly
skip= ped 1000
MM: Initialise page allocator for 396000(396000)-10000000(10000= 000)
MM: done
Demand map pfns at 10001000-0000002010001000.
Initia= lising timer interface
Initialising console ... done.
gnttab_table ma= pped at 0000000010001000.
getenv(OCAMLRUNPARAM) ->=3B null
getenv(C= AMLRUNPARAM) ->=3B null
getenv(PATH) ->=3B null
Unsupported funct= ion lseek called in Mini-OS kernel
Unsupported function lseek called in = Mini-OS kernel
Unsupported function lseek called in Mini-OS kernel
ge= tenv(OCAMLRUNPARAM) ->=3B null
getenv(CAMLRUNPARAM) ->=3B null
ge= tenv(TMPDIR) ->=3B null
getenv(TEMP) ->=3B null
Netif: add resume= hook
Netif.connect tap0: could not find device
Fatal error: exceptio= n Failure("\n\nnet_tap0: device tap0 not found (available =3D [ =3B ])\= nIf using a tap device=2C is tun/tap enabled and have you permissions?\n\n"= )
Raised at file "src/core/lwt.ml"=2C line 788=2C characters 22-23
Ca= lled from file "lib/main.ml"=2C line 58=2C characters 10-20
Called from = file "main.ml"=2C line 85=2C characters 2-28
Mirage exiting with status = 2
Do_exit called!
base is 0x27ff20 caller is 0x1237b1
base is 0x23= 2530 caller is 0x0
base is 0x141783 caller is 0x5241570000000000
base= is 0x65676172696d Page fault at linear address 656761726975=2C rip 13d607= =2C regs 000000000027fe38=2C sp 27fee0=2C our_sp 000000000027fdf8=2C code 0=
RIP: e030:[<=3B000000000013d607>=3B]
RSP: e02b:000000000027fee0=  =3B EFLAGS: 00010006
RAX: 0000000000000017 RBX: 000065676172696d RC= X: 0000000000000743
RDX: 0000000000000743 RSI: 000000000027fd30 RDI: 000= 0000000000004
RBP: 000000000027ff20 R08: 0000000000000742 R09: 000000000= 0000020
R10: 0000000000000017 R11: 0000000000000000 R12: 000000000000000= 0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
b= ase is 0x27ff20 caller is 0x1237b1
base is 0x232530 caller is 0x0
bas= e is 0x141783 caller is 0x5241570000000000
base is 0x65676172696d Page f= ault in pagetable walk (access to invalid memory?).


=0A=
= --_73dfdf26-8b66-45a8-8bdd-5aacd0a8f36e_-- --===============0677013366819534089== 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 --===============0677013366819534089==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 14:57:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 14:57:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnTQE-0003g5-3W; Wed, 29 Apr 2015 14:57:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnTQC-0003g0-Uu for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 14:57:09 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 84/19-26324-341F0455; Wed, 29 Apr 2015 14:57:07 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1430319425!10999735!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14547 invoked from network); 29 Apr 2015 14:57:05 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2015 14:57:05 -0000 Received: from mfilter13-d.gandi.net (mfilter13-d.gandi.net [217.70.178.141]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 743C3FB86E for ; Wed, 29 Apr 2015 16:57:05 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter13-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter13-d.gandi.net (mfilter13-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id ZsW62PvOcUsx for ; Wed, 29 Apr 2015 16:57:03 +0200 (CEST) X-Originating-IP: 131.111.184.18 Received: from [172.17.25.72] (global-1-18.nat.csx.cam.ac.uk [131.111.184.18]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id A0A5AFB8DC for ; Wed, 29 Apr 2015 16:57:03 +0200 (CEST) Message-ID: <5540F108.2030004@somerandomidiot.com> Date: Wed, 29 Apr 2015 15:56:08 +0100 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org> In-Reply-To: Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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-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 04/29/2015 11:58 AM, Justin Cormack wrote: > On 29 April 2015 at 10:35, Thomas Gazagnaire wrote: >> Third, when I managed to get one of the network samples building, for >> example "ping", I couldn't get the unikernel running locally with a tun/tap >> device I created. Even though I use tapctl to create a tap0 device owned by >> my user account, just like the tutorial advises, when I go to execute the >> unikernel I still get this error: >> >> Fatal error: exception Failure("net_tap0") >> Raised at file "src/core/lwt.ml", line 788, characters 22-23 >> Called from file "src/unix/lwt_main.ml", line 34, characters 8-18 >> Called from file "main.ml", line 47, characters 2-28 >> >> >> This is rather cryptic but might indicate that you need to run the command >> using sudo. > What does strace show here? It might be permissions but if you made > the device owned by your user account it shouldnt be. You may need to > make /dev/net/tun world read and write (which is safe to do). On 14.04.2, I need to run with sudo even if the device is owned by my user, I've made it with tunctl -u me, and the mode is u+rwx, otherwise strace shows open("/dev/net/tun", O_RDWR) = 4 ioctl(4, TUNSETIFF, 0x7fffb7dd0a20) = 0 ioctl(4, TUNSETPERSIST, 0) = 0 fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 ioctl(5, SIOCGIFFLAGS, {ifr_name="tap0", ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0 ioctl(5, SIOCSIFFLAGS, {ifr_name="tap0", ???}) = -1 EPERM (Operation not permitted) So you may need to run it with elevated privileges even if it seems like you should be able to get away with running it as yourself. (Thanks for the bug report; attempting to reproduce it got me to actually use the tap interface for the first time.) -Mindy _______________________________________________ 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 Apr 29 14:57:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 14:57:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnTQE-0003g5-3W; Wed, 29 Apr 2015 14:57:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnTQC-0003g0-Uu for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 14:57:09 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 84/19-26324-341F0455; Wed, 29 Apr 2015 14:57:07 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1430319425!10999735!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14547 invoked from network); 29 Apr 2015 14:57:05 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2015 14:57:05 -0000 Received: from mfilter13-d.gandi.net (mfilter13-d.gandi.net [217.70.178.141]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 743C3FB86E for ; Wed, 29 Apr 2015 16:57:05 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter13-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter13-d.gandi.net (mfilter13-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id ZsW62PvOcUsx for ; Wed, 29 Apr 2015 16:57:03 +0200 (CEST) X-Originating-IP: 131.111.184.18 Received: from [172.17.25.72] (global-1-18.nat.csx.cam.ac.uk [131.111.184.18]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id A0A5AFB8DC for ; Wed, 29 Apr 2015 16:57:03 +0200 (CEST) Message-ID: <5540F108.2030004@somerandomidiot.com> Date: Wed, 29 Apr 2015 15:56:08 +0100 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org> In-Reply-To: Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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-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 04/29/2015 11:58 AM, Justin Cormack wrote: > On 29 April 2015 at 10:35, Thomas Gazagnaire wrote: >> Third, when I managed to get one of the network samples building, for >> example "ping", I couldn't get the unikernel running locally with a tun/tap >> device I created. Even though I use tapctl to create a tap0 device owned by >> my user account, just like the tutorial advises, when I go to execute the >> unikernel I still get this error: >> >> Fatal error: exception Failure("net_tap0") >> Raised at file "src/core/lwt.ml", line 788, characters 22-23 >> Called from file "src/unix/lwt_main.ml", line 34, characters 8-18 >> Called from file "main.ml", line 47, characters 2-28 >> >> >> This is rather cryptic but might indicate that you need to run the command >> using sudo. > What does strace show here? It might be permissions but if you made > the device owned by your user account it shouldnt be. You may need to > make /dev/net/tun world read and write (which is safe to do). On 14.04.2, I need to run with sudo even if the device is owned by my user, I've made it with tunctl -u me, and the mode is u+rwx, otherwise strace shows open("/dev/net/tun", O_RDWR) = 4 ioctl(4, TUNSETIFF, 0x7fffb7dd0a20) = 0 ioctl(4, TUNSETPERSIST, 0) = 0 fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 ioctl(5, SIOCGIFFLAGS, {ifr_name="tap0", ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0 ioctl(5, SIOCSIFFLAGS, {ifr_name="tap0", ???}) = -1 EPERM (Operation not permitted) So you may need to run it with elevated privileges even if it seems like you should be able to get away with running it as yourself. (Thanks for the bug report; attempting to reproduce it got me to actually use the tap interface for the first time.) -Mindy _______________________________________________ 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 Apr 29 15:50:27 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 15:50: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 1YnUFg-0005DB-84; Wed, 29 Apr 2015 15:50:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnUFf-0005D6-Ov for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 15:50:19 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 45/44-23180-ABDF0455; Wed, 29 Apr 2015 15:50:18 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1430322618!13308872!1 X-Originating-IP: [157.55.2.36] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5949 invoked from network); 29 Apr 2015 15:50:18 -0000 Received: from dub004-omc3s27.hotmail.com (HELO DUB004-OMC3S27.hotmail.com) (157.55.2.36) by server-2.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 15:50:18 -0000 Received: from DUB128-W24 ([157.55.2.7]) by DUB004-OMC3S27.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 08:50:17 -0700 X-TMN: [CUUlWJAnK85eyi51ZTnLGOGNwVHY/H3U] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Wed, 29 Apr 2015 15:50:17 +0000 Importance: Normal In-Reply-To: References: , , <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org>, , , , <1153A97D-9C94-4F8D-BBE8-A2E5434582A9@recoil.org>, MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 15:50:17.0998 (UTC) FILETIME=[30D80AE0:01D08294] Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============7397721714665428399==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7397721714665428399== Content-Type: multipart/alternative; boundary="_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_" --_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ah=2C without wishing to hijack this thread=2C I've noticed that my mistake= is not setting up tap0=3B so doing a: sudo ifconfig tap0 192.168.1.2 netmask 255.255.255.0 gives a: SIOCSIFADDR: No such device tap0: ERROR while getting interface flags: No such device Surely this should simply create the device? = --_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ah=2C without wishing to hijack = this thread=2C I've noticed that my mistake is not setting up tap0=3B so do= ing a:

sudo ifconfig tap0 192.168.1.2 netmask 255.255.255.0

g= ives a:

SIOCSIFADDR: No such = device
tap0: ERROR while getting interface flags: No such device

= Surely this should simply create the device?
=
= --_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_-- --===============7397721714665428399== 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 --===============7397721714665428399==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 15:50:27 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 15:50: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 1YnUFg-0005DB-84; Wed, 29 Apr 2015 15:50:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnUFf-0005D6-Ov for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 15:50:19 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 45/44-23180-ABDF0455; Wed, 29 Apr 2015 15:50:18 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1430322618!13308872!1 X-Originating-IP: [157.55.2.36] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5949 invoked from network); 29 Apr 2015 15:50:18 -0000 Received: from dub004-omc3s27.hotmail.com (HELO DUB004-OMC3S27.hotmail.com) (157.55.2.36) by server-2.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 15:50:18 -0000 Received: from DUB128-W24 ([157.55.2.7]) by DUB004-OMC3S27.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 08:50:17 -0700 X-TMN: [CUUlWJAnK85eyi51ZTnLGOGNwVHY/H3U] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Wed, 29 Apr 2015 15:50:17 +0000 Importance: Normal In-Reply-To: References: , , <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org>, , , , <1153A97D-9C94-4F8D-BBE8-A2E5434582A9@recoil.org>, MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 15:50:17.0998 (UTC) FILETIME=[30D80AE0:01D08294] Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============7397721714665428399==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7397721714665428399== Content-Type: multipart/alternative; boundary="_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_" --_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ah=2C without wishing to hijack this thread=2C I've noticed that my mistake= is not setting up tap0=3B so doing a: sudo ifconfig tap0 192.168.1.2 netmask 255.255.255.0 gives a: SIOCSIFADDR: No such device tap0: ERROR while getting interface flags: No such device Surely this should simply create the device? = --_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ah=2C without wishing to hijack = this thread=2C I've noticed that my mistake is not setting up tap0=3B so do= ing a:

sudo ifconfig tap0 192.168.1.2 netmask 255.255.255.0

g= ives a:

SIOCSIFADDR: No such = device
tap0: ERROR while getting interface flags: No such device

= Surely this should simply create the device?
=
= --_e613ae10-3bac-4e9b-b38f-9f58dc1d882a_-- --===============7397721714665428399== 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 --===============7397721714665428399==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 17:08:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:08: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 1YnVSy-0000z4-AN; Wed, 29 Apr 2015 17:08:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVSw-0000yw-MM for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:08:06 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id 00/72-13722-5FF01455; Wed, 29 Apr 2015 17:08:05 +0000 X-Env-Sender: robertream@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1430327284!13330636!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12488 invoked from network); 29 Apr 2015 17:08:04 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2015 17:08:04 -0000 Received: by wgyo15 with SMTP id o15so35524637wgy.2 for ; Wed, 29 Apr 2015 10:08:04 -0700 (PDT) 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=T+jszty3vb0lMr9MD9NrcQ66+ppWH9uX1VXJuh3TWqg=; b=M8acc8fEwRmqgEHZ2WCTfyLW17+NnQ60mmMvxh18Yxs7MYy7SyFqBUl5UvTNpzE86w Q2T11ecT7Q6/MhammhsJSaNmYSBl9DqVyqtKoXWxZMjWkIKlwGnkKeHInam1tDpDc3pO qXjveA/XmcW15X+pf4PlSSqWv6v4p2PwjDlkCcNxT3kuS5Xyy+0qcDjYeKl7cN+OxGAF Oo8Awq3GDB3D9bui85EY1MUSaX+CWsOxuhcKcOqgan3u61x31siECqzoZUOkdlZzXBjZ tarZ9cmeJj5l/3Kz7t1pHPaTwcn8WODw9aZ7TU9xYthaMT11Bv4ujnD9ilqKLKBPjLBa DrQw== MIME-Version: 1.0 X-Received: by 10.180.187.12 with SMTP id fo12mr10779229wic.40.1430327284014; Wed, 29 Apr 2015 10:08:04 -0700 (PDT) Received: by 10.194.162.197 with HTTP; Wed, 29 Apr 2015 10:08:03 -0700 (PDT) In-Reply-To: <5540F108.2030004@somerandomidiot.com> References: <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org> <5540F108.2030004@somerandomidiot.com> Date: Wed, 29 Apr 2015 10:08:03 -0700 Message-ID: From: Robert Ream To: Mindy Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============0059000543382160479==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0059000543382160479== Content-Type: multipart/alternative; boundary=001a11c2693ead26960514e005e0 --001a11c2693ead26960514e005e0 Content-Type: text/plain; charset=UTF-8 Thanks Mindy and everyone for all the input! Doing a make clean and running with elevated privileges has moved the bar, I'm now building and running the network samples. Yay! But... I've run into more issues. First, this is the output when I run sudo ./mir-ping: plugging into tap0 with mac c2:9d:56:19:d7:2c.. Netif: connect tap0 starting... ARP: sending gratuitous from 10.0.0.2 IP6 Netif: error, terminating listen loop done! I'm not sure what I was suppose to expect as the output but it says there was an error and that "IP6" is actually coloured red so that can't be good? But the error might be related to the second issue that I see which is that whenever I run a network related sample, the tap0 interface just disappears, or maybe gets deleted. I am unfortunately fairly inexperienced with tun/tap so I'm not sure if this is the expected behaviour, but I'm guessing these two errors might be related to each other and I'm on the verge of success if I fix this last problem. -Robert On Wed, Apr 29, 2015 at 7:56 AM, Mindy wrote: > > > On 04/29/2015 11:58 AM, Justin Cormack wrote: > >> On 29 April 2015 at 10:35, Thomas Gazagnaire >> wrote: >> >>> Third, when I managed to get one of the network samples building, for >>> example "ping", I couldn't get the unikernel running locally with a >>> tun/tap >>> device I created. Even though I use tapctl to create a tap0 device owned >>> by >>> my user account, just like the tutorial advises, when I go to execute the >>> unikernel I still get this error: >>> >>> Fatal error: exception Failure("net_tap0") >>> Raised at file "src/core/lwt.ml", line 788, characters 22-23 >>> Called from file "src/unix/lwt_main.ml", line 34, characters 8-18 >>> Called from file "main.ml", line 47, characters 2-28 >>> >>> >>> This is rather cryptic but might indicate that you need to run the >>> command >>> using sudo. >>> >> What does strace show here? It might be permissions but if you made >> the device owned by your user account it shouldnt be. You may need to >> make /dev/net/tun world read and write (which is safe to do). >> > On 14.04.2, I need to run with sudo even if the device is owned by my > user, I've made it with tunctl -u me, and the mode is u+rwx, otherwise > strace shows > > open("/dev/net/tun", O_RDWR) = 4 > ioctl(4, TUNSETIFF, 0x7fffb7dd0a20) = 0 > ioctl(4, TUNSETPERSIST, 0) = 0 > fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) > fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0 > socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 > ioctl(5, SIOCGIFFLAGS, {ifr_name="tap0", > ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0 > ioctl(5, SIOCSIFFLAGS, {ifr_name="tap0", ???}) = -1 EPERM (Operation not > permitted) > > So you may need to run it with elevated privileges even if it seems like > you should be able to get away with running it as yourself. > > (Thanks for the bug report; attempting to reproduce it got me to actually > use the tap interface for the first time.) > > -Mindy > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11c2693ead26960514e005e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Mindy and everyone for all the input! Doing a = make clean and running with elevated privileges has moved the bar, I'm = now building and running the network samples. Yay!

But... I've r= un into more issues.

First, this is the output when I run sudo ./mir= -ping:

plugging into tap0 with mac c2:9d:56:19:d7:2c..
Netif: con= nect tap0
starting...
ARP: sending gratuitous from 10.0.0.2
IP6Netif: error, terminating listen loop
done!

I'm not sure wha= t I was suppose to expect as the output but it says there was an error and = that "IP6" is actually coloured red so that can't be good? Bu= t the error might be related to the second issue that I see which is that w= henever I run a network related sample, the tap0 interface just disappears,= or maybe gets deleted. I am unfortunately fairly inexperienced with tun/ta= p so I'm not sure if this is the expected behaviour, but I'm guessi= ng these two errors might be related to each other and I'm on the verge= of success if I fix this last problem.

-Robert
=


On Wed, Apr 29, 2015 at 7:56 AM, Mindy <mindy@somerandomidiot.= com> wrote:


On 04/29/2015 11:58 AM, Justin Cormack wrote:
On 29 April 2015 at 10:35, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
Third, when I managed to get one of the network samples building, for
example "ping", I couldn't get the unikernel running locally = with a tun/tap
device I created. Even though I use tapctl to create a tap0 device owned by=
my user account, just like the tutorial advises, when I go to execute the unikernel I still get this error:

Fatal error: exception Failure("net_tap0")
Raised at file "src/core/l= wt.ml", line 788, characters 22-23
Called from file "src/unix/lwt_main.ml", line 34, characters 8-18
Called from file "main.ml= ", line 47, characters 2-28


This is rather cryptic but might indicate that you need to run the command<= br> using sudo.
What does strace show here? It might be permissions but if you made
the device owned by your user account it shouldnt be. You may need to
make /dev/net/tun world read and write (which is safe to do).
On 14.04.2, I need to run with sudo even if the device is owned by my user,= I've made it with tunctl -u me, and the mode is u+rwx, otherwise strac= e shows

open("/dev/net/tun", O_RDWR)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =3D 4
ioctl(4, TUNSETIFF, 0x7fffb7dd0a20)=C2=A0 =C2=A0 =C2=A0=3D 0
ioctl(4, TUNSETPERSIST, 0)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =3D 0
fcntl(4, F_GETFL)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D 0x8002 (flags O_RDWR|O_LARGEFILE)
fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) =3D 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) =3D 5
ioctl(5, SIOCGIFFLAGS, {ifr_name=3D"tap0", ifr_flags=3DIFF_BROADC= AST|IFF_MULTICAST}) =3D 0
ioctl(5, SIOCSIFFLAGS, {ifr_name=3D"tap0", ???}) =3D -1 EPERM (Op= eration not permitted)

So you may need to run it with elevated privileges even if it seems like yo= u should be able to get away with running it as yourself.

(Thanks for the bug report; attempting to reproduce it got me to actually u= se the tap interface for the first time.)

-Mindy


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

--001a11c2693ead26960514e005e0-- --===============0059000543382160479== 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 --===============0059000543382160479==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 17:08:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:08: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 1YnVSy-0000z4-AN; Wed, 29 Apr 2015 17:08:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVSw-0000yw-MM for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:08:06 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id 00/72-13722-5FF01455; Wed, 29 Apr 2015 17:08:05 +0000 X-Env-Sender: robertream@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1430327284!13330636!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12488 invoked from network); 29 Apr 2015 17:08:04 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2015 17:08:04 -0000 Received: by wgyo15 with SMTP id o15so35524637wgy.2 for ; Wed, 29 Apr 2015 10:08:04 -0700 (PDT) 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=T+jszty3vb0lMr9MD9NrcQ66+ppWH9uX1VXJuh3TWqg=; b=M8acc8fEwRmqgEHZ2WCTfyLW17+NnQ60mmMvxh18Yxs7MYy7SyFqBUl5UvTNpzE86w Q2T11ecT7Q6/MhammhsJSaNmYSBl9DqVyqtKoXWxZMjWkIKlwGnkKeHInam1tDpDc3pO qXjveA/XmcW15X+pf4PlSSqWv6v4p2PwjDlkCcNxT3kuS5Xyy+0qcDjYeKl7cN+OxGAF Oo8Awq3GDB3D9bui85EY1MUSaX+CWsOxuhcKcOqgan3u61x31siECqzoZUOkdlZzXBjZ tarZ9cmeJj5l/3Kz7t1pHPaTwcn8WODw9aZ7TU9xYthaMT11Bv4ujnD9ilqKLKBPjLBa DrQw== MIME-Version: 1.0 X-Received: by 10.180.187.12 with SMTP id fo12mr10779229wic.40.1430327284014; Wed, 29 Apr 2015 10:08:04 -0700 (PDT) Received: by 10.194.162.197 with HTTP; Wed, 29 Apr 2015 10:08:03 -0700 (PDT) In-Reply-To: <5540F108.2030004@somerandomidiot.com> References: <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org> <5540F108.2030004@somerandomidiot.com> Date: Wed, 29 Apr 2015 10:08:03 -0700 Message-ID: From: Robert Ream To: Mindy Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============0059000543382160479==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0059000543382160479== Content-Type: multipart/alternative; boundary=001a11c2693ead26960514e005e0 --001a11c2693ead26960514e005e0 Content-Type: text/plain; charset=UTF-8 Thanks Mindy and everyone for all the input! Doing a make clean and running with elevated privileges has moved the bar, I'm now building and running the network samples. Yay! But... I've run into more issues. First, this is the output when I run sudo ./mir-ping: plugging into tap0 with mac c2:9d:56:19:d7:2c.. Netif: connect tap0 starting... ARP: sending gratuitous from 10.0.0.2 IP6 Netif: error, terminating listen loop done! I'm not sure what I was suppose to expect as the output but it says there was an error and that "IP6" is actually coloured red so that can't be good? But the error might be related to the second issue that I see which is that whenever I run a network related sample, the tap0 interface just disappears, or maybe gets deleted. I am unfortunately fairly inexperienced with tun/tap so I'm not sure if this is the expected behaviour, but I'm guessing these two errors might be related to each other and I'm on the verge of success if I fix this last problem. -Robert On Wed, Apr 29, 2015 at 7:56 AM, Mindy wrote: > > > On 04/29/2015 11:58 AM, Justin Cormack wrote: > >> On 29 April 2015 at 10:35, Thomas Gazagnaire >> wrote: >> >>> Third, when I managed to get one of the network samples building, for >>> example "ping", I couldn't get the unikernel running locally with a >>> tun/tap >>> device I created. Even though I use tapctl to create a tap0 device owned >>> by >>> my user account, just like the tutorial advises, when I go to execute the >>> unikernel I still get this error: >>> >>> Fatal error: exception Failure("net_tap0") >>> Raised at file "src/core/lwt.ml", line 788, characters 22-23 >>> Called from file "src/unix/lwt_main.ml", line 34, characters 8-18 >>> Called from file "main.ml", line 47, characters 2-28 >>> >>> >>> This is rather cryptic but might indicate that you need to run the >>> command >>> using sudo. >>> >> What does strace show here? It might be permissions but if you made >> the device owned by your user account it shouldnt be. You may need to >> make /dev/net/tun world read and write (which is safe to do). >> > On 14.04.2, I need to run with sudo even if the device is owned by my > user, I've made it with tunctl -u me, and the mode is u+rwx, otherwise > strace shows > > open("/dev/net/tun", O_RDWR) = 4 > ioctl(4, TUNSETIFF, 0x7fffb7dd0a20) = 0 > ioctl(4, TUNSETPERSIST, 0) = 0 > fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) > fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0 > socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 > ioctl(5, SIOCGIFFLAGS, {ifr_name="tap0", > ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0 > ioctl(5, SIOCSIFFLAGS, {ifr_name="tap0", ???}) = -1 EPERM (Operation not > permitted) > > So you may need to run it with elevated privileges even if it seems like > you should be able to get away with running it as yourself. > > (Thanks for the bug report; attempting to reproduce it got me to actually > use the tap interface for the first time.) > > -Mindy > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11c2693ead26960514e005e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Mindy and everyone for all the input! Doing a = make clean and running with elevated privileges has moved the bar, I'm = now building and running the network samples. Yay!

But... I've r= un into more issues.

First, this is the output when I run sudo ./mir= -ping:

plugging into tap0 with mac c2:9d:56:19:d7:2c..
Netif: con= nect tap0
starting...
ARP: sending gratuitous from 10.0.0.2
IP6Netif: error, terminating listen loop
done!

I'm not sure wha= t I was suppose to expect as the output but it says there was an error and = that "IP6" is actually coloured red so that can't be good? Bu= t the error might be related to the second issue that I see which is that w= henever I run a network related sample, the tap0 interface just disappears,= or maybe gets deleted. I am unfortunately fairly inexperienced with tun/ta= p so I'm not sure if this is the expected behaviour, but I'm guessi= ng these two errors might be related to each other and I'm on the verge= of success if I fix this last problem.

-Robert
=


On Wed, Apr 29, 2015 at 7:56 AM, Mindy <mindy@somerandomidiot.= com> wrote:


On 04/29/2015 11:58 AM, Justin Cormack wrote:
On 29 April 2015 at 10:35, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
Third, when I managed to get one of the network samples building, for
example "ping", I couldn't get the unikernel running locally = with a tun/tap
device I created. Even though I use tapctl to create a tap0 device owned by=
my user account, just like the tutorial advises, when I go to execute the unikernel I still get this error:

Fatal error: exception Failure("net_tap0")
Raised at file "src/core/l= wt.ml", line 788, characters 22-23
Called from file "src/unix/lwt_main.ml", line 34, characters 8-18
Called from file "main.ml= ", line 47, characters 2-28


This is rather cryptic but might indicate that you need to run the command<= br> using sudo.
What does strace show here? It might be permissions but if you made
the device owned by your user account it shouldnt be. You may need to
make /dev/net/tun world read and write (which is safe to do).
On 14.04.2, I need to run with sudo even if the device is owned by my user,= I've made it with tunctl -u me, and the mode is u+rwx, otherwise strac= e shows

open("/dev/net/tun", O_RDWR)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =3D 4
ioctl(4, TUNSETIFF, 0x7fffb7dd0a20)=C2=A0 =C2=A0 =C2=A0=3D 0
ioctl(4, TUNSETPERSIST, 0)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =3D 0
fcntl(4, F_GETFL)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D 0x8002 (flags O_RDWR|O_LARGEFILE)
fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) =3D 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) =3D 5
ioctl(5, SIOCGIFFLAGS, {ifr_name=3D"tap0", ifr_flags=3DIFF_BROADC= AST|IFF_MULTICAST}) =3D 0
ioctl(5, SIOCSIFFLAGS, {ifr_name=3D"tap0", ???}) =3D -1 EPERM (Op= eration not permitted)

So you may need to run it with elevated privileges even if it seems like yo= u should be able to get away with running it as yourself.

(Thanks for the bug report; attempting to reproduce it got me to actually u= se the tap interface for the first time.)

-Mindy


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

--001a11c2693ead26960514e005e0-- --===============0059000543382160479== 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 --===============0059000543382160479==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 17:17:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:17:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVcN-0001Dd-6H; Wed, 29 Apr 2015 17:17:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVcL-0001DY-AF for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:17:49 +0000 Received: from [193.109.254.147] by server-13.bemta-14.messagelabs.com id 99/9E-26939-C3211455; Wed, 29 Apr 2015 17:17:48 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1430327867!7922109!1 X-Originating-IP: [157.55.2.26] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2150 invoked from network); 29 Apr 2015 17:17:47 -0000 Received: from dub004-omc3s17.hotmail.com (HELO DUB004-OMC3S17.hotmail.com) (157.55.2.26) by server-16.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 17:17:47 -0000 Received: from DUB128-W74 ([157.55.2.8]) by DUB004-OMC3S17.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 10:17:47 -0700 X-TMN: [1RbyRcW9TeKWa2ayWkaReHUczGXR+IYn] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Wed, 29 Apr 2015 17:17:46 +0000 Importance: Normal In-Reply-To: References: , , , , <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org>, , , , , , , , <1153A97D-9C94-4F8D-BBE8-A2E5434582A9@recoil.org>, , , MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 17:17:47.0247 (UTC) FILETIME=[69A3DFF0:01D082A0] Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============1119198338686252402==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1119198338686252402== Content-Type: multipart/alternative; boundary="_39315884-239c-48af-a3d0-add21bf4ccba_" --_39315884-239c-48af-a3d0-add21bf4ccba_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= OK=2C to add the tap on ubuntu trusty amd64=2C you need tunctl=2C which is = loaded using: sudo apt-get install uml-utilities runnning: 'tunctl' followed by 'sudo ifconfig tap0 192.168.1.2 netmask 255.= 255.255.0' will do the trick. But I guess you knew all of this =3B) =0A= = --_39315884-239c-48af-a3d0-add21bf4ccba_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
=0A= =0A= =0A=
OK=2C to add the tap on ubuntu trusty amd64=2C you need tu= nctl=2C which is loaded using:

sudo apt-get install uml-utilities
runnning: 'tunctl' followed by 'sudo ifconfig tap0 192.168.1.2 netmask= 255.255.255.0' will do the trick.

But I guess you knew all of this = =3B)
=0A=
= --_39315884-239c-48af-a3d0-add21bf4ccba_-- --===============1119198338686252402== 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 --===============1119198338686252402==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 17:17:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:17:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVcN-0001Dd-6H; Wed, 29 Apr 2015 17:17:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVcL-0001DY-AF for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:17:49 +0000 Received: from [193.109.254.147] by server-13.bemta-14.messagelabs.com id 99/9E-26939-C3211455; Wed, 29 Apr 2015 17:17:48 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1430327867!7922109!1 X-Originating-IP: [157.55.2.26] X-SpamReason: No, hits=0.7 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2150 invoked from network); 29 Apr 2015 17:17:47 -0000 Received: from dub004-omc3s17.hotmail.com (HELO DUB004-OMC3S17.hotmail.com) (157.55.2.26) by server-16.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 17:17:47 -0000 Received: from DUB128-W74 ([157.55.2.8]) by DUB004-OMC3S17.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 10:17:47 -0700 X-TMN: [1RbyRcW9TeKWa2ayWkaReHUczGXR+IYn] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Wed, 29 Apr 2015 17:17:46 +0000 Importance: Normal In-Reply-To: References: , , , , <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org>, , , , , , , , <1153A97D-9C94-4F8D-BBE8-A2E5434582A9@recoil.org>, , , MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 17:17:47.0247 (UTC) FILETIME=[69A3DFF0:01D082A0] Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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="===============1119198338686252402==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1119198338686252402== Content-Type: multipart/alternative; boundary="_39315884-239c-48af-a3d0-add21bf4ccba_" --_39315884-239c-48af-a3d0-add21bf4ccba_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= OK=2C to add the tap on ubuntu trusty amd64=2C you need tunctl=2C which is = loaded using: sudo apt-get install uml-utilities runnning: 'tunctl' followed by 'sudo ifconfig tap0 192.168.1.2 netmask 255.= 255.255.0' will do the trick. But I guess you knew all of this =3B) =0A= = --_39315884-239c-48af-a3d0-add21bf4ccba_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
=0A= =0A= =0A=
OK=2C to add the tap on ubuntu trusty amd64=2C you need tu= nctl=2C which is loaded using:

sudo apt-get install uml-utilities
runnning: 'tunctl' followed by 'sudo ifconfig tap0 192.168.1.2 netmask= 255.255.255.0' will do the trick.

But I guess you knew all of this = =3B)
=0A=
= --_39315884-239c-48af-a3d0-add21bf4ccba_-- --===============1119198338686252402== 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 --===============1119198338686252402==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 17:32:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:32:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVqC-0001dD-AT; Wed, 29 Apr 2015 17:32:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVqA-0001d8-9h for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:32:06 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id F8/AA-26324-59511455; Wed, 29 Apr 2015 17:32:05 +0000 X-Env-Sender: n.oje.bar@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1430328724!8589146!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13223 invoked from network); 29 Apr 2015 17:32:04 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2015 17:32:04 -0000 Received: by wiun10 with SMTP id n10so74305008wiu.1 for ; Wed, 29 Apr 2015 10:32:04 -0700 (PDT) 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=A2I5k3xwZ5J1BVA5RF0z4rdE81mfSSb29+UqiVODAug=; b=ch8XcvkwHe6IWe+OIvDAdkzfkOVrwYr5fs8praMc2WB0niu6CF25sieXoYYUjOtVu2 zv2tMWVe2JljoyUNlBjTPqwlcvkYy4j0KZPwlc+blnHTCiu0nq30/vgD7Yl6aPdGVhKs TCGt8njXUINmOoH8NxFhz1YnyxSia03n0vW4El2OtAyYN53P64aysgXfDNicKzZo/dx3 fq4tPKoDD1m8aLpmjAkxaNxlLHAzp9UqNGLiSra3LcRBqCwt4Mfnn4bZwuRvhtDVCJxH 6xwoTy8W20f2hgPHxL7XMCKWDhtHe3bT0UQj9nmjns7D/Ohj6zaWqgRamrJHm3izfW9L PJiQ== MIME-Version: 1.0 X-Received: by 10.180.14.193 with SMTP id r1mr10806287wic.47.1430328720615; Wed, 29 Apr 2015 10:32:00 -0700 (PDT) Received: by 10.27.126.138 with HTTP; Wed, 29 Apr 2015 10:32:00 -0700 (PDT) In-Reply-To: References: <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org> <5540F108.2030004@somerandomidiot.com> Date: Wed, 29 Apr 2015 18:32:00 +0100 X-Google-Sender-Auth: NG67m7ClRneLKUtbEb8D8oLyo1M Message-ID: From: Nicolas Ojeda Bar To: Robert Ream Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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 Dear Robert, Don't worry about "IP6" appearing in red - it just means that the example ping program does not handle IPv6 traffic: see https://github.com/mirage/mirage-skeleton/blob/master/ping/unikernel.ml#L48 for the relevant line (I guess the debug output leaves a lot to be desired...). There is an IPv6-aware ping program in mirage-skeleton/ping6. Best wishes, Nicolas On Wed, Apr 29, 2015 at 6:08 PM, Robert Ream wrote: > Thanks Mindy and everyone for all the input! Doing a make clean and running > with elevated privileges has moved the bar, I'm now building and running the > network samples. Yay! > > But... I've run into more issues. > > First, this is the output when I run sudo ./mir-ping: > > plugging into tap0 with mac c2:9d:56:19:d7:2c.. > Netif: connect tap0 > starting... > ARP: sending gratuitous from 10.0.0.2 > IP6 > Netif: error, terminating listen loop > done! > > I'm not sure what I was suppose to expect as the output but it says there > was an error and that "IP6" is actually coloured red so that can't be good? > But the error might be related to the second issue that I see which is that > whenever I run a network related sample, the tap0 interface just disappears, > or maybe gets deleted. I am unfortunately fairly inexperienced with tun/tap > so I'm not sure if this is the expected behaviour, but I'm guessing these > two errors might be related to each other and I'm on the verge of success if > I fix this last problem. > > -Robert > > > On Wed, Apr 29, 2015 at 7:56 AM, Mindy wrote: >> >> >> >> On 04/29/2015 11:58 AM, Justin Cormack wrote: >>> >>> On 29 April 2015 at 10:35, Thomas Gazagnaire >>> wrote: >>>> >>>> Third, when I managed to get one of the network samples building, for >>>> example "ping", I couldn't get the unikernel running locally with a >>>> tun/tap >>>> device I created. Even though I use tapctl to create a tap0 device owned >>>> by >>>> my user account, just like the tutorial advises, when I go to execute >>>> the >>>> unikernel I still get this error: >>>> >>>> Fatal error: exception Failure("net_tap0") >>>> Raised at file "src/core/lwt.ml", line 788, characters 22-23 >>>> Called from file "src/unix/lwt_main.ml", line 34, characters 8-18 >>>> Called from file "main.ml", line 47, characters 2-28 >>>> >>>> >>>> This is rather cryptic but might indicate that you need to run the >>>> command >>>> using sudo. >>> >>> What does strace show here? It might be permissions but if you made >>> the device owned by your user account it shouldnt be. You may need to >>> make /dev/net/tun world read and write (which is safe to do). >> >> On 14.04.2, I need to run with sudo even if the device is owned by my >> user, I've made it with tunctl -u me, and the mode is u+rwx, otherwise >> strace shows >> >> open("/dev/net/tun", O_RDWR) = 4 >> ioctl(4, TUNSETIFF, 0x7fffb7dd0a20) = 0 >> ioctl(4, TUNSETPERSIST, 0) = 0 >> fcntl(4, F_GETFL) = 0x8002 (flags >> O_RDWR|O_LARGEFILE) >> fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0 >> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 >> ioctl(5, SIOCGIFFLAGS, {ifr_name="tap0", >> ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0 >> ioctl(5, SIOCSIFFLAGS, {ifr_name="tap0", ???}) = -1 EPERM (Operation not >> permitted) >> >> So you may need to run it with elevated privileges even if it seems like >> you should be able to get away with running it as yourself. >> >> (Thanks for the bug report; attempting to reproduce it got me to actually >> use the tap interface for the first time.) >> >> -Mindy >> >> >> _______________________________________________ >> 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 > _______________________________________________ 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 Apr 29 17:32:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:32:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVqC-0001dD-AT; Wed, 29 Apr 2015 17:32:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVqA-0001d8-9h for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:32:06 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id F8/AA-26324-59511455; Wed, 29 Apr 2015 17:32:05 +0000 X-Env-Sender: n.oje.bar@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1430328724!8589146!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13223 invoked from network); 29 Apr 2015 17:32:04 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2015 17:32:04 -0000 Received: by wiun10 with SMTP id n10so74305008wiu.1 for ; Wed, 29 Apr 2015 10:32:04 -0700 (PDT) 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=A2I5k3xwZ5J1BVA5RF0z4rdE81mfSSb29+UqiVODAug=; b=ch8XcvkwHe6IWe+OIvDAdkzfkOVrwYr5fs8praMc2WB0niu6CF25sieXoYYUjOtVu2 zv2tMWVe2JljoyUNlBjTPqwlcvkYy4j0KZPwlc+blnHTCiu0nq30/vgD7Yl6aPdGVhKs TCGt8njXUINmOoH8NxFhz1YnyxSia03n0vW4El2OtAyYN53P64aysgXfDNicKzZo/dx3 fq4tPKoDD1m8aLpmjAkxaNxlLHAzp9UqNGLiSra3LcRBqCwt4Mfnn4bZwuRvhtDVCJxH 6xwoTy8W20f2hgPHxL7XMCKWDhtHe3bT0UQj9nmjns7D/Ohj6zaWqgRamrJHm3izfW9L PJiQ== MIME-Version: 1.0 X-Received: by 10.180.14.193 with SMTP id r1mr10806287wic.47.1430328720615; Wed, 29 Apr 2015 10:32:00 -0700 (PDT) Received: by 10.27.126.138 with HTTP; Wed, 29 Apr 2015 10:32:00 -0700 (PDT) In-Reply-To: References: <07CD6C17-3703-4888-A0D7-0C78FFADB14E@gazagnaire.org> <5540F108.2030004@somerandomidiot.com> Date: Wed, 29 Apr 2015 18:32:00 +0100 X-Google-Sender-Auth: NG67m7ClRneLKUtbEb8D8oLyo1M Message-ID: From: Nicolas Ojeda Bar To: Robert Ream Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.4 errors on install and mirage-skeleton build 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 Dear Robert, Don't worry about "IP6" appearing in red - it just means that the example ping program does not handle IPv6 traffic: see https://github.com/mirage/mirage-skeleton/blob/master/ping/unikernel.ml#L48 for the relevant line (I guess the debug output leaves a lot to be desired...). There is an IPv6-aware ping program in mirage-skeleton/ping6. Best wishes, Nicolas On Wed, Apr 29, 2015 at 6:08 PM, Robert Ream wrote: > Thanks Mindy and everyone for all the input! Doing a make clean and running > with elevated privileges has moved the bar, I'm now building and running the > network samples. Yay! > > But... I've run into more issues. > > First, this is the output when I run sudo ./mir-ping: > > plugging into tap0 with mac c2:9d:56:19:d7:2c.. > Netif: connect tap0 > starting... > ARP: sending gratuitous from 10.0.0.2 > IP6 > Netif: error, terminating listen loop > done! > > I'm not sure what I was suppose to expect as the output but it says there > was an error and that "IP6" is actually coloured red so that can't be good? > But the error might be related to the second issue that I see which is that > whenever I run a network related sample, the tap0 interface just disappears, > or maybe gets deleted. I am unfortunately fairly inexperienced with tun/tap > so I'm not sure if this is the expected behaviour, but I'm guessing these > two errors might be related to each other and I'm on the verge of success if > I fix this last problem. > > -Robert > > > On Wed, Apr 29, 2015 at 7:56 AM, Mindy wrote: >> >> >> >> On 04/29/2015 11:58 AM, Justin Cormack wrote: >>> >>> On 29 April 2015 at 10:35, Thomas Gazagnaire >>> wrote: >>>> >>>> Third, when I managed to get one of the network samples building, for >>>> example "ping", I couldn't get the unikernel running locally with a >>>> tun/tap >>>> device I created. Even though I use tapctl to create a tap0 device owned >>>> by >>>> my user account, just like the tutorial advises, when I go to execute >>>> the >>>> unikernel I still get this error: >>>> >>>> Fatal error: exception Failure("net_tap0") >>>> Raised at file "src/core/lwt.ml", line 788, characters 22-23 >>>> Called from file "src/unix/lwt_main.ml", line 34, characters 8-18 >>>> Called from file "main.ml", line 47, characters 2-28 >>>> >>>> >>>> This is rather cryptic but might indicate that you need to run the >>>> command >>>> using sudo. >>> >>> What does strace show here? It might be permissions but if you made >>> the device owned by your user account it shouldnt be. You may need to >>> make /dev/net/tun world read and write (which is safe to do). >> >> On 14.04.2, I need to run with sudo even if the device is owned by my >> user, I've made it with tunctl -u me, and the mode is u+rwx, otherwise >> strace shows >> >> open("/dev/net/tun", O_RDWR) = 4 >> ioctl(4, TUNSETIFF, 0x7fffb7dd0a20) = 0 >> ioctl(4, TUNSETPERSIST, 0) = 0 >> fcntl(4, F_GETFL) = 0x8002 (flags >> O_RDWR|O_LARGEFILE) >> fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0 >> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 >> ioctl(5, SIOCGIFFLAGS, {ifr_name="tap0", >> ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0 >> ioctl(5, SIOCSIFFLAGS, {ifr_name="tap0", ???}) = -1 EPERM (Operation not >> permitted) >> >> So you may need to run it with elevated privileges even if it seems like >> you should be able to get away with running it as yourself. >> >> (Thanks for the bug report; attempting to reproduce it got me to actually >> use the tap interface for the first time.) >> >> -Mindy >> >> >> _______________________________________________ >> 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 > _______________________________________________ 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 Apr 29 17:33:53 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:33: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 1YnVrt-0001fO-HC; Wed, 29 Apr 2015 17:33:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVrs-0001fJ-2x for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:33:52 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id E4/B9-16511-FF511455; Wed, 29 Apr 2015 17:33:51 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1430328829!13248212!1 X-Originating-IP: [157.55.2.16] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4054 invoked from network); 29 Apr 2015 17:33:49 -0000 Received: from dub004-omc3s7.hotmail.com (HELO DUB004-OMC3S7.hotmail.com) (157.55.2.16) by server-3.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 17:33:49 -0000 Received: from DUB128-W59 ([157.55.2.8]) by DUB004-OMC3S7.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 10:33:49 -0700 X-TMN: [An83nVBcRUwmn0CJDoa0C69MLyx/hCck] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Wed, 29 Apr 2015 17:33:48 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 17:33:49.0027 (UTC) FILETIME=[A6E7DB30:01D082A2] Subject: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============8796629453916805752==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8796629453916805752== Content-Type: multipart/alternative; boundary="_33a3361e-2e9c-4d6d-adac-fc67121c86fa_" --_33a3361e-2e9c-4d6d-adac-fc67121c86fa_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Having just got tap to work on ubuntu=2Ctrusty=2Cam64=2C I have just tried = to do the same on the Cubieboard2 and it seems that I'm unable to actually = create /dev/net/tun. If I do the following: sudo mkdir /dev/net sudo mknod /dev/net/tun c 10 200 sudo chmod 0666 /dev/net/tun sudo modprobe tun gives :=20 modprobe: FATAL: Module tun not found. Doing a : sudo tunctl gives: Failed to open '/dev/net/tun' : No such device Does anyone have any experience on this? Cheers Nick = --_33a3361e-2e9c-4d6d-adac-fc67121c86fa_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Having just got tap to work on u= buntu=2Ctrusty=2Cam64=2C I have just tried to do the same on the Cubieboard= 2 and it seems that I'm unable to actually create /dev/net/tun.

If I= do the following:

sudo mkdir /dev/net
sudo mknod /dev/net/tun c = 10 200
sudo chmod 0666 /dev/net/tun
sudo modprobe tun

gives : =

modprobe: FATAL: Module tun not found.

Doing a :

sudo= tunctl

gives:

Failed to open '/dev/net/tun' : No such device=


Does anyone have any experience on this?

Cheers
Nick<= br>
= --_33a3361e-2e9c-4d6d-adac-fc67121c86fa_-- --===============8796629453916805752== 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 --===============8796629453916805752==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 17:33:53 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 17:33: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 1YnVrt-0001fO-HC; Wed, 29 Apr 2015 17:33:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnVrs-0001fJ-2x for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 17:33:52 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id E4/B9-16511-FF511455; Wed, 29 Apr 2015 17:33:51 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1430328829!13248212!1 X-Originating-IP: [157.55.2.16] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4054 invoked from network); 29 Apr 2015 17:33:49 -0000 Received: from dub004-omc3s7.hotmail.com (HELO DUB004-OMC3S7.hotmail.com) (157.55.2.16) by server-3.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 29 Apr 2015 17:33:49 -0000 Received: from DUB128-W59 ([157.55.2.8]) by DUB004-OMC3S7.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 10:33:49 -0700 X-TMN: [An83nVBcRUwmn0CJDoa0C69MLyx/hCck] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Wed, 29 Apr 2015 17:33:48 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 29 Apr 2015 17:33:49.0027 (UTC) FILETIME=[A6E7DB30:01D082A2] Subject: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============8796629453916805752==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8796629453916805752== Content-Type: multipart/alternative; boundary="_33a3361e-2e9c-4d6d-adac-fc67121c86fa_" --_33a3361e-2e9c-4d6d-adac-fc67121c86fa_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Having just got tap to work on ubuntu=2Ctrusty=2Cam64=2C I have just tried = to do the same on the Cubieboard2 and it seems that I'm unable to actually = create /dev/net/tun. If I do the following: sudo mkdir /dev/net sudo mknod /dev/net/tun c 10 200 sudo chmod 0666 /dev/net/tun sudo modprobe tun gives :=20 modprobe: FATAL: Module tun not found. Doing a : sudo tunctl gives: Failed to open '/dev/net/tun' : No such device Does anyone have any experience on this? Cheers Nick = --_33a3361e-2e9c-4d6d-adac-fc67121c86fa_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Having just got tap to work on u= buntu=2Ctrusty=2Cam64=2C I have just tried to do the same on the Cubieboard= 2 and it seems that I'm unable to actually create /dev/net/tun.

If I= do the following:

sudo mkdir /dev/net
sudo mknod /dev/net/tun c = 10 200
sudo chmod 0666 /dev/net/tun
sudo modprobe tun

gives : =

modprobe: FATAL: Module tun not found.

Doing a :

sudo= tunctl

gives:

Failed to open '/dev/net/tun' : No such device=


Does anyone have any experience on this?

Cheers
Nick<= br>
= --_33a3361e-2e9c-4d6d-adac-fc67121c86fa_-- --===============8796629453916805752== 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 --===============8796629453916805752==-- From mirageos-devel-bounces@lists.xenproject.org Wed Apr 29 18:20:57 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 18:20: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 1YnWbK-0003Bl-JD; Wed, 29 Apr 2015 18:20:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnWbI-0003Bg-Nb for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 18:20:48 +0000 Received: from [85.158.137.68] by server-10.bemta-3.messagelabs.com id F8/4A-14673-FF021455; Wed, 29 Apr 2015 18:20:47 +0000 X-Env-Sender: justin@specialbusservice.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1430331647!11055496!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27521 invoked from network); 29 Apr 2015 18:20:47 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2015 18:20:47 -0000 Received: by wgin8 with SMTP id n8so37571437wgi.0 for ; Wed, 29 Apr 2015 11:20:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=specialbusservice.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VdnhBAYIc5dPmxhGW9Prhp6zof6SGpneJXd700oXGCU=; b=H25Jv7AE6SB4NfrQnAGndct1Taz+aJpN1jr+cNVBCXhsb9mneVzk25TcSJ+09v50s7 OLIKi+QNQcZBhQKFmBgVsAQTaoKN5irj8lfxzSUOKo28K7NvXKnMVS4SK7758C3k7iGO rUvJBi4FlZYIQ9eDZ8bEmbSHfeimGTWfyGgUo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=VdnhBAYIc5dPmxhGW9Prhp6zof6SGpneJXd700oXGCU=; b=CLdpXBzFSu7fwHCuow141brczhKRRR47ipidw4oYlLLgJWAetSXqrdr6tdOOfFbAlz RigndMFGWrJFCacxJEgjx4PvIgAZ8olU/UqbPyH7OWedJbah47cAxjv/5lwsZ4B5y4Wv Dyv8c56NqvDBxnJ7BsWkj/lT2kGOQ405o4MkuOgtrI23K/TGHmW+klzq9tZ9/dEsC7vK sCo4QH0s0sKB1TyTfz0Oq3SDJv4R/cRc66xLAk+r5uIyA2adVhA2FOJpbTks5KeSDgqx +E65DxRt/pyTAoBryOTMny1rBlbG8cv1YKEuFStEbzoKAO/Fs1Mxb7kc1HhT5KJ3fFcw 8HdQ== X-Gm-Message-State: ALoCoQl85pJ/0hpwNouhSsrj3MxCUrRcyPmbqnLonT/Ts2gPh8Neg/RaD/HaXzvKaa/iXdzFfOkc MIME-Version: 1.0 X-Received: by 10.194.236.66 with SMTP id us2mr823655wjc.54.1430331646859; Wed, 29 Apr 2015 11:20:46 -0700 (PDT) Received: by 10.28.13.85 with HTTP; Wed, 29 Apr 2015 11:20:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 29 Apr 2015 19:20:46 +0100 Message-ID: From: Justin Cormack To: Nick Betteridge Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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 29 April 2015 at 18:33, Nick Betteridge wrote: > modprobe: FATAL: Module tun not found. > > Doing a : > > sudo tunctl > > gives: > > Failed to open '/dev/net/tun' : No such device > > > Does anyone have any experience on this? Yes, the precompiled kernels for Arm are generally missing lots of modules for usually no good reason. It is rather frustrating - you need to compile a kernel with the tun facility enabled as a module or built in. Where did your kernel come from, a distro? File a bug please if so! Justin _______________________________________________ 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 Apr 29 18:20:57 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 29 Apr 2015 18:20: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 1YnWbK-0003Bl-JD; Wed, 29 Apr 2015 18:20:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnWbI-0003Bg-Nb for mirageos-devel@lists.xenproject.org; Wed, 29 Apr 2015 18:20:48 +0000 Received: from [85.158.137.68] by server-10.bemta-3.messagelabs.com id F8/4A-14673-FF021455; Wed, 29 Apr 2015 18:20:47 +0000 X-Env-Sender: justin@specialbusservice.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1430331647!11055496!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27521 invoked from network); 29 Apr 2015 18:20:47 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2015 18:20:47 -0000 Received: by wgin8 with SMTP id n8so37571437wgi.0 for ; Wed, 29 Apr 2015 11:20:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=specialbusservice.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VdnhBAYIc5dPmxhGW9Prhp6zof6SGpneJXd700oXGCU=; b=H25Jv7AE6SB4NfrQnAGndct1Taz+aJpN1jr+cNVBCXhsb9mneVzk25TcSJ+09v50s7 OLIKi+QNQcZBhQKFmBgVsAQTaoKN5irj8lfxzSUOKo28K7NvXKnMVS4SK7758C3k7iGO rUvJBi4FlZYIQ9eDZ8bEmbSHfeimGTWfyGgUo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=VdnhBAYIc5dPmxhGW9Prhp6zof6SGpneJXd700oXGCU=; b=CLdpXBzFSu7fwHCuow141brczhKRRR47ipidw4oYlLLgJWAetSXqrdr6tdOOfFbAlz RigndMFGWrJFCacxJEgjx4PvIgAZ8olU/UqbPyH7OWedJbah47cAxjv/5lwsZ4B5y4Wv Dyv8c56NqvDBxnJ7BsWkj/lT2kGOQ405o4MkuOgtrI23K/TGHmW+klzq9tZ9/dEsC7vK sCo4QH0s0sKB1TyTfz0Oq3SDJv4R/cRc66xLAk+r5uIyA2adVhA2FOJpbTks5KeSDgqx +E65DxRt/pyTAoBryOTMny1rBlbG8cv1YKEuFStEbzoKAO/Fs1Mxb7kc1HhT5KJ3fFcw 8HdQ== X-Gm-Message-State: ALoCoQl85pJ/0hpwNouhSsrj3MxCUrRcyPmbqnLonT/Ts2gPh8Neg/RaD/HaXzvKaa/iXdzFfOkc MIME-Version: 1.0 X-Received: by 10.194.236.66 with SMTP id us2mr823655wjc.54.1430331646859; Wed, 29 Apr 2015 11:20:46 -0700 (PDT) Received: by 10.28.13.85 with HTTP; Wed, 29 Apr 2015 11:20:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 29 Apr 2015 19:20:46 +0100 Message-ID: From: Justin Cormack To: Nick Betteridge Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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 29 April 2015 at 18:33, Nick Betteridge wrote: > modprobe: FATAL: Module tun not found. > > Doing a : > > sudo tunctl > > gives: > > Failed to open '/dev/net/tun' : No such device > > > Does anyone have any experience on this? Yes, the precompiled kernels for Arm are generally missing lots of modules for usually no good reason. It is rather frustrating - you need to compile a kernel with the tun facility enabled as a module or built in. Where did your kernel come from, a distro? File a bug please if so! Justin _______________________________________________ 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 Apr 30 00:28:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 00:28:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YncLP-0004H8-F2; Thu, 30 Apr 2015 00:28:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YncLN-0004H3-Pl for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 00:28:45 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id E2/58-26324-C3771455; Thu, 30 Apr 2015 00:28:44 +0000 X-Env-Sender: lukedunstan81@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1430353724!11114030!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5028 invoked from network); 30 Apr 2015 00:28:44 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 00:28:44 -0000 Received: by laat2 with SMTP id t2so32506181laa.1 for ; Wed, 29 Apr 2015 17:28:43 -0700 (PDT) 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=Cy8qs8QFZuuhYYHEgRDW5jkJbhOcqpOWooyV88KeGU8=; b=RvYaJdeTzgtpOHelzmEmzuRtYp+BPY6EJZfoFoVZMi7lOsYAFjpE8o7aBorHEAIBgR 4Vj/ZdT7doryxS2BeGpuuKevXKTeopDkw7Sv+aGJ1ds+mTLLVP53LpoOdydx4PrbBL7H z/C051tPB9FFGIzoNw9GqwLlk7qzSSFEhIzrTfo6Ii29SBZ5Y3hwRXGDjgMEtDZclRxs IDPKxLiun43KLZPv5o8HoX34Kx7c2t3s6G95oOjB3NsmmB+jqAroNabI6/xqQ3n8cxm1 bRggSHUzSZC4efAxU8jLWO35jrCUd9Z48btY5g6AIvDBZp+CerGOSqbE0gqiquB3chot v8yw== MIME-Version: 1.0 X-Received: by 10.152.8.6 with SMTP id n6mr1400647laa.116.1430353723741; Wed, 29 Apr 2015 17:28:43 -0700 (PDT) Received: by 10.112.119.197 with HTTP; Wed, 29 Apr 2015 17:28:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Apr 2015 08:28:43 +0800 Message-ID: From: Luke Dunstan To: Justin Cormack Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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 If the image was the one downloaded from openmirage.org, then it was built using these scripts: https://github.com/mirage/xen-arm-builder If you want to change the kernel config and rebuild it then you should be able to just do the kernel step manually without rebuilding the whole image. If you are using that image though, you'll probably find it more interesting to use Xen rather than Unix+tuntap. Luke On 30 April 2015 at 02:20, Justin Cormack wrote: > On 29 April 2015 at 18:33, Nick Betteridge wrote: >> modprobe: FATAL: Module tun not found. >> >> Doing a : >> >> sudo tunctl >> >> gives: >> >> Failed to open '/dev/net/tun' : No such device >> >> >> Does anyone have any experience on this? > > Yes, the precompiled kernels for Arm are generally missing lots of > modules for usually no good reason. It is rather frustrating - you > need to compile a kernel with the tun facility enabled as a module or > built in. > > Where did your kernel come from, a distro? File a bug please if so! > > Justin > > _______________________________________________ > 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 Thu Apr 30 00:28:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 00:28:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YncLP-0004H8-F2; Thu, 30 Apr 2015 00:28:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YncLN-0004H3-Pl for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 00:28:45 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id E2/58-26324-C3771455; Thu, 30 Apr 2015 00:28:44 +0000 X-Env-Sender: lukedunstan81@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1430353724!11114030!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5028 invoked from network); 30 Apr 2015 00:28:44 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 00:28:44 -0000 Received: by laat2 with SMTP id t2so32506181laa.1 for ; Wed, 29 Apr 2015 17:28:43 -0700 (PDT) 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=Cy8qs8QFZuuhYYHEgRDW5jkJbhOcqpOWooyV88KeGU8=; b=RvYaJdeTzgtpOHelzmEmzuRtYp+BPY6EJZfoFoVZMi7lOsYAFjpE8o7aBorHEAIBgR 4Vj/ZdT7doryxS2BeGpuuKevXKTeopDkw7Sv+aGJ1ds+mTLLVP53LpoOdydx4PrbBL7H z/C051tPB9FFGIzoNw9GqwLlk7qzSSFEhIzrTfo6Ii29SBZ5Y3hwRXGDjgMEtDZclRxs IDPKxLiun43KLZPv5o8HoX34Kx7c2t3s6G95oOjB3NsmmB+jqAroNabI6/xqQ3n8cxm1 bRggSHUzSZC4efAxU8jLWO35jrCUd9Z48btY5g6AIvDBZp+CerGOSqbE0gqiquB3chot v8yw== MIME-Version: 1.0 X-Received: by 10.152.8.6 with SMTP id n6mr1400647laa.116.1430353723741; Wed, 29 Apr 2015 17:28:43 -0700 (PDT) Received: by 10.112.119.197 with HTTP; Wed, 29 Apr 2015 17:28:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Apr 2015 08:28:43 +0800 Message-ID: From: Luke Dunstan To: Justin Cormack Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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 If the image was the one downloaded from openmirage.org, then it was built using these scripts: https://github.com/mirage/xen-arm-builder If you want to change the kernel config and rebuild it then you should be able to just do the kernel step manually without rebuilding the whole image. If you are using that image though, you'll probably find it more interesting to use Xen rather than Unix+tuntap. Luke On 30 April 2015 at 02:20, Justin Cormack wrote: > On 29 April 2015 at 18:33, Nick Betteridge wrote: >> modprobe: FATAL: Module tun not found. >> >> Doing a : >> >> sudo tunctl >> >> gives: >> >> Failed to open '/dev/net/tun' : No such device >> >> >> Does anyone have any experience on this? > > Yes, the precompiled kernels for Arm are generally missing lots of > modules for usually no good reason. It is rather frustrating - you > need to compile a kernel with the tun facility enabled as a module or > built in. > > Where did your kernel come from, a distro? File a bug please if so! > > Justin > > _______________________________________________ > 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 Thu Apr 30 06:44:05 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 06:44: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 1YniCU-0000Jo-2U; Thu, 30 Apr 2015 06:43:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniCS-0000Jj-Oa for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 06:43:56 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id F9/23-30165-B2FC1455; Thu, 30 Apr 2015 06:43:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-31.messagelabs.com!1430376234!11095279!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25649 invoked from network); 30 Apr 2015 06:43:55 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 06:43:55 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id e2950c35; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 30 Apr 2015 07:43:53 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 30 Apr 2015 07:43:53 +0100 Message-Id: References: To: Luke Dunstan X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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 But also, please do feel free to submit a pull request to the xen-arm-builder to build the missing modules by default. It was a fairly arbitrary set that we picked to just get Xen up and running, and there's no harm in building things like tuntap in so that all the Mirage backend modes are available. -anil > On 30 Apr 2015, at 01:28, Luke Dunstan wrote: > > If the image was the one downloaded from openmirage.org, then it was > built using these scripts: https://github.com/mirage/xen-arm-builder > > If you want to change the kernel config and rebuild it then you should > be able to just do the kernel step manually without rebuilding the > whole image. > > If you are using that image though, you'll probably find it more > interesting to use Xen rather than Unix+tuntap. > > Luke > > > On 30 April 2015 at 02:20, Justin Cormack wrote: >> On 29 April 2015 at 18:33, Nick Betteridge wrote: >>> modprobe: FATAL: Module tun not found. >>> >>> Doing a : >>> >>> sudo tunctl >>> >>> gives: >>> >>> Failed to open '/dev/net/tun' : No such device >>> >>> >>> Does anyone have any experience on this? >> >> Yes, the precompiled kernels for Arm are generally missing lots of >> modules for usually no good reason. It is rather frustrating - you >> need to compile a kernel with the tun facility enabled as a module or >> built in. >> >> Where did your kernel come from, a distro? File a bug please if so! >> >> Justin >> >> _______________________________________________ >> 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 > _______________________________________________ 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 Apr 30 06:44:05 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 06:44: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 1YniCU-0000Jo-2U; Thu, 30 Apr 2015 06:43:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniCS-0000Jj-Oa for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 06:43:56 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id F9/23-30165-B2FC1455; Thu, 30 Apr 2015 06:43:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-31.messagelabs.com!1430376234!11095279!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25649 invoked from network); 30 Apr 2015 06:43:55 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 06:43:55 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id e2950c35; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 30 Apr 2015 07:43:53 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 30 Apr 2015 07:43:53 +0100 Message-Id: References: To: Luke Dunstan X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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 But also, please do feel free to submit a pull request to the xen-arm-builder to build the missing modules by default. It was a fairly arbitrary set that we picked to just get Xen up and running, and there's no harm in building things like tuntap in so that all the Mirage backend modes are available. -anil > On 30 Apr 2015, at 01:28, Luke Dunstan wrote: > > If the image was the one downloaded from openmirage.org, then it was > built using these scripts: https://github.com/mirage/xen-arm-builder > > If you want to change the kernel config and rebuild it then you should > be able to just do the kernel step manually without rebuilding the > whole image. > > If you are using that image though, you'll probably find it more > interesting to use Xen rather than Unix+tuntap. > > Luke > > > On 30 April 2015 at 02:20, Justin Cormack wrote: >> On 29 April 2015 at 18:33, Nick Betteridge wrote: >>> modprobe: FATAL: Module tun not found. >>> >>> Doing a : >>> >>> sudo tunctl >>> >>> gives: >>> >>> Failed to open '/dev/net/tun' : No such device >>> >>> >>> Does anyone have any experience on this? >> >> Yes, the precompiled kernels for Arm are generally missing lots of >> modules for usually no good reason. It is rather frustrating - you >> need to compile a kernel with the tun facility enabled as a module or >> built in. >> >> Where did your kernel come from, a distro? File a bug please if so! >> >> Justin >> >> _______________________________________________ >> 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 > _______________________________________________ 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 Apr 30 06:52:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 06:52:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniKP-0000fb-Q8; Thu, 30 Apr 2015 06:52:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniKN-0000fT-OI for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 06:52:07 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 9A/D9-23827-611D1455; Thu, 30 Apr 2015 06:52:06 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1430376725!13466194!1 X-Originating-IP: [157.55.2.105] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28760 invoked from network); 30 Apr 2015 06:52:05 -0000 Received: from dub004-omc4s30.hotmail.com (HELO DUB004-OMC4S30.hotmail.com) (157.55.2.105) by server-14.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 30 Apr 2015 06:52:05 -0000 Received: from DUB128-W17 ([157.55.2.71]) by DUB004-OMC4S30.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 23:52:04 -0700 X-TMN: [r3sKBYPPb2nIzDFgImxbionwHtWHNjD6] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: Luke Dunstan Date: Thu, 30 Apr 2015 06:52:04 +0000 Importance: Normal In-Reply-To: References: , , MIME-Version: 1.0 X-OriginalArrivalTime: 30 Apr 2015 06:52:04.0996 (UTC) FILETIME=[2B20BC40:01D08312] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============8041626844280674255==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8041626844280674255== Content-Type: multipart/alternative; boundary="_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_" --_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=20 > If you are using that image though=2C you'll probably find it more > interesting to use Xen rather than Unix+tuntap. >=20 There failure I got was from using xen - I'll look at xen-arm-builder = --_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
>=3B
>=3B If you ar= e using that image though=2C you'll probably find it more
>=3B interes= ting to use Xen rather than Unix+tuntap.
>=3B

There failure I = got was from using xen - I'll look at xen-arm-builder
=
= --_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_-- --===============8041626844280674255== 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 --===============8041626844280674255==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 06:52:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 06:52:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniKP-0000fb-Q8; Thu, 30 Apr 2015 06:52:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniKN-0000fT-OI for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 06:52:07 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 9A/D9-23827-611D1455; Thu, 30 Apr 2015 06:52:06 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1430376725!13466194!1 X-Originating-IP: [157.55.2.105] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28760 invoked from network); 30 Apr 2015 06:52:05 -0000 Received: from dub004-omc4s30.hotmail.com (HELO DUB004-OMC4S30.hotmail.com) (157.55.2.105) by server-14.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 30 Apr 2015 06:52:05 -0000 Received: from DUB128-W17 ([157.55.2.71]) by DUB004-OMC4S30.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 23:52:04 -0700 X-TMN: [r3sKBYPPb2nIzDFgImxbionwHtWHNjD6] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: Luke Dunstan Date: Thu, 30 Apr 2015 06:52:04 +0000 Importance: Normal In-Reply-To: References: , , MIME-Version: 1.0 X-OriginalArrivalTime: 30 Apr 2015 06:52:04.0996 (UTC) FILETIME=[2B20BC40:01D08312] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============8041626844280674255==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8041626844280674255== Content-Type: multipart/alternative; boundary="_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_" --_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=20 > If you are using that image though=2C you'll probably find it more > interesting to use Xen rather than Unix+tuntap. >=20 There failure I got was from using xen - I'll look at xen-arm-builder = --_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
>=3B
>=3B If you ar= e using that image though=2C you'll probably find it more
>=3B interes= ting to use Xen rather than Unix+tuntap.
>=3B

There failure I = got was from using xen - I'll look at xen-arm-builder
=
= --_d0aa34cb-f3b7-4e36-9efb-3a7707477b8c_-- --===============8041626844280674255== 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 --===============8041626844280674255==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 06:54:34 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 06:54: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 1YniMj-0000i8-4M; Thu, 30 Apr 2015 06:54:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniMh-0000i3-1D for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 06:54:31 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 42/68-23555-6A1D1455; Thu, 30 Apr 2015 06:54:30 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1430376868!11176168!1 X-Originating-IP: [157.55.2.91] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30539 invoked from network); 30 Apr 2015 06:54:28 -0000 Received: from dub004-omc4s16.hotmail.com (HELO DUB004-OMC4S16.hotmail.com) (157.55.2.91) by server-11.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 30 Apr 2015 06:54:28 -0000 Received: from DUB128-W18 ([157.55.2.73]) by DUB004-OMC4S16.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 23:54:28 -0700 X-TMN: [BE+1xhgkgTVJHEHYzzpGdRoAtsggH0fv] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: Anil Madhavapeddy Date: Thu, 30 Apr 2015 06:54:27 +0000 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 30 Apr 2015 06:54:28.0289 (UTC) FILETIME=[80898310:01D08312] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============8887872048418799470==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8887872048418799470== Content-Type: multipart/alternative; boundary="_e492cc10-2858-455d-9cc2-c886a0691a5f_" --_e492cc10-2858-455d-9cc2-c886a0691a5f_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=20 > But also=2C please do feel free to submit a pull request to the xen-arm-b= uilder > to build the missing modules by default. It was a fairly arbitrary set th= at > we picked to just get Xen up and running=2C and there's no harm in buildi= ng > things like tuntap in so that all the Mirage backend modes are available. >=20 I'll do this - I also need to revisit cubieboard4 - sunxi are promising cub= ieboard4 support in their next release Cheers Nick = --_e492cc10-2858-455d-9cc2-c886a0691a5f_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B
>=3B But a= lso=2C please do feel free to submit a pull request to the xen-arm-builder<= br>>=3B to build the missing modules by default. It was a fairly arbitrar= y set that
>=3B we picked to just get Xen up and running=2C and there'= s no harm in building
>=3B things like tuntap in so that all the Mirag= e backend modes are available.
>=3B

I'll do this - I also need= to revisit cubieboard4 - sunxi are promising cubieboard4 support in their = next release

Cheers
Nick
= --_e492cc10-2858-455d-9cc2-c886a0691a5f_-- --===============8887872048418799470== 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 --===============8887872048418799470==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 06:54:34 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 06:54: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 1YniMj-0000i8-4M; Thu, 30 Apr 2015 06:54:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YniMh-0000i3-1D for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 06:54:31 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id 42/68-23555-6A1D1455; Thu, 30 Apr 2015 06:54:30 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1430376868!11176168!1 X-Originating-IP: [157.55.2.91] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30539 invoked from network); 30 Apr 2015 06:54:28 -0000 Received: from dub004-omc4s16.hotmail.com (HELO DUB004-OMC4S16.hotmail.com) (157.55.2.91) by server-11.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 30 Apr 2015 06:54:28 -0000 Received: from DUB128-W18 ([157.55.2.73]) by DUB004-OMC4S16.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 29 Apr 2015 23:54:28 -0700 X-TMN: [BE+1xhgkgTVJHEHYzzpGdRoAtsggH0fv] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: Anil Madhavapeddy Date: Thu, 30 Apr 2015 06:54:27 +0000 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 30 Apr 2015 06:54:28.0289 (UTC) FILETIME=[80898310:01D08312] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============8887872048418799470==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8887872048418799470== Content-Type: multipart/alternative; boundary="_e492cc10-2858-455d-9cc2-c886a0691a5f_" --_e492cc10-2858-455d-9cc2-c886a0691a5f_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=20 > But also=2C please do feel free to submit a pull request to the xen-arm-b= uilder > to build the missing modules by default. It was a fairly arbitrary set th= at > we picked to just get Xen up and running=2C and there's no harm in buildi= ng > things like tuntap in so that all the Mirage backend modes are available. >=20 I'll do this - I also need to revisit cubieboard4 - sunxi are promising cub= ieboard4 support in their next release Cheers Nick = --_e492cc10-2858-455d-9cc2-c886a0691a5f_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B
>=3B But a= lso=2C please do feel free to submit a pull request to the xen-arm-builder<= br>>=3B to build the missing modules by default. It was a fairly arbitrar= y set that
>=3B we picked to just get Xen up and running=2C and there'= s no harm in building
>=3B things like tuntap in so that all the Mirag= e backend modes are available.
>=3B

I'll do this - I also need= to revisit cubieboard4 - sunxi are promising cubieboard4 support in their = next release

Cheers
Nick
= --_e492cc10-2858-455d-9cc2-c886a0691a5f_-- --===============8887872048418799470== 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 --===============8887872048418799470==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 07:12:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 07:12: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 1Ynie9-0001R1-Uo; Thu, 30 Apr 2015 07:12:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ynie8-0001Qw-Re for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 07:12:33 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 30/BC-20070-FD5D1455; Thu, 30 Apr 2015 07:12:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1430377950!8375346!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31636 invoked from network); 30 Apr 2015 07:12:30 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 07:12:30 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 80f68411; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 30 Apr 2015 08:12:29 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 30 Apr 2015 08:12:28 +0100 Message-Id: References: To: Nick Betteridge X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============2956659877767834098==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2956659877767834098== Content-Type: multipart/alternative; boundary="Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63" --Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 30 Apr 2015, at 07:54, Nick Betteridge = wrote: >=20 >=20 > >=20 > > But also, please do feel free to submit a pull request to the = xen-arm-builder > > to build the missing modules by default. It was a fairly arbitrary = set that > > we picked to just get Xen up and running, and there's no harm in = building > > things like tuntap in so that all the Mirage backend modes are = available. > >=20 >=20 > I'll do this - I also need to revisit cubieboard4 - sunxi are = promising cubieboard4 support in their next release Good point -- I need to order one as well. On the ARM hardware front, = I've been pointed to a couple of interesting targets: - USB Armory: ARM A8 on a USB stick running Debian; = http://www.inversepath.com/usbarmory.html = - Scaleway continues to make progress on Xen/ARM on their ARM cloud = https://github.com/scaleway/kernel-tools/issues/14 = -anil= --Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 30 Apr 2015, at 07:54, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:


> 
> But also, please do feel free to submit a = pull request to the xen-arm-builder
> to build the missing modules by default. It = was a fairly arbitrary set that
> we picked to just get = Xen up and running, and there's no harm in building
> things like tuntap in so that all the = Mirage backend modes are available.
> 

I'll do this - I also need to revisit = cubieboard4 - sunxi are promising cubieboard4 support in their next = release

Good = point -- I need to order one as well.  On the ARM hardware front, = I've been pointed to a couple of interesting targets:

- USB Armory: ARM A8 on = a USB stick running Debian; http://www.inversepath.com/usbarmory.html
- Scaleway continues to make progress on Xen/ARM on their ARM = cloud https://github.com/scaleway/kernel-tools/issues/14

-anil
= --Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63-- --===============2956659877767834098== 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 --===============2956659877767834098==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 07:12:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 07:12: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 1Ynie9-0001R1-Uo; Thu, 30 Apr 2015 07:12:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ynie8-0001Qw-Re for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 07:12:33 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 30/BC-20070-FD5D1455; Thu, 30 Apr 2015 07:12:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1430377950!8375346!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31636 invoked from network); 30 Apr 2015 07:12:30 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 07:12:30 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 80f68411; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 30 Apr 2015 08:12:29 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 30 Apr 2015 08:12:28 +0100 Message-Id: References: To: Nick Betteridge X-Mailer: Apple Mail (2.2098) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] /dev/net/tun on Cubieboard2 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="===============2956659877767834098==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2956659877767834098== Content-Type: multipart/alternative; boundary="Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63" --Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 30 Apr 2015, at 07:54, Nick Betteridge = wrote: >=20 >=20 > >=20 > > But also, please do feel free to submit a pull request to the = xen-arm-builder > > to build the missing modules by default. It was a fairly arbitrary = set that > > we picked to just get Xen up and running, and there's no harm in = building > > things like tuntap in so that all the Mirage backend modes are = available. > >=20 >=20 > I'll do this - I also need to revisit cubieboard4 - sunxi are = promising cubieboard4 support in their next release Good point -- I need to order one as well. On the ARM hardware front, = I've been pointed to a couple of interesting targets: - USB Armory: ARM A8 on a USB stick running Debian; = http://www.inversepath.com/usbarmory.html = - Scaleway continues to make progress on Xen/ARM on their ARM cloud = https://github.com/scaleway/kernel-tools/issues/14 = -anil= --Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 30 Apr 2015, at 07:54, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:


> 
> But also, please do feel free to submit a = pull request to the xen-arm-builder
> to build the missing modules by default. It = was a fairly arbitrary set that
> we picked to just get = Xen up and running, and there's no harm in building
> things like tuntap in so that all the = Mirage backend modes are available.
> 

I'll do this - I also need to revisit = cubieboard4 - sunxi are promising cubieboard4 support in their next = release

Good = point -- I need to order one as well.  On the ARM hardware front, = I've been pointed to a couple of interesting targets:

- USB Armory: ARM A8 on = a USB stick running Debian; http://www.inversepath.com/usbarmory.html
- Scaleway continues to make progress on Xen/ARM on their ARM = cloud https://github.com/scaleway/kernel-tools/issues/14

-anil
= --Apple-Mail=_AA898090-7D1F-48A3-AD7B-B8F19D9A6B63-- --===============2956659877767834098== 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 --===============2956659877767834098==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 10:21:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 10:21: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 1Ynlai-0006xu-7D; Thu, 30 Apr 2015 10:21:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ynlah-0006xl-74 for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 10:21:11 +0000 Received: from [193.109.254.147] by server-2.bemta-14.messagelabs.com id F6/9F-14319-61202455; Thu, 30 Apr 2015 10:21:10 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1430389269!13537920!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13063 invoked from network); 30 Apr 2015 10:21:09 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 10:21:09 -0000 Received: by widdi4 with SMTP id di4so13305293wid.0 for ; Thu, 30 Apr 2015 03:21:09 -0700 (PDT) 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=FIuGGTavN0EsXSJL/bPeAsfRHLXTUZUZSK/Hgu3J+7I=; b=hl0gvfIcQVno5o/gQIidx7ErXukeOUBkkO/6RW7YKhQp1IVY47S9TiSwqZgMGGpFOy uV3xTVGdmXfm2FNE8rV5kFiAiqL6HiPcGjT7lsAMK7g3H8N6N5NPqtIF/e2+UsEyE+oe Miv/b/jjLJwXgqESpiQUsRzFJ5GfrkCSSjHBhZegBaVYQTinSf5IUgKf5SxeaW9sjxD5 aUQFi850c/nIdx5SEj+K0so6g68yuNFRLZyeo20e8VtcHREuTDyO+A2kMDoONs5/x76T /ueOsIFJ9mR9D6UKRmR6HzuMN1HmI97Pqgi/T7zbR0LdqhLbTa0ZSH2dP6Z4CDBSamOF kl8w== X-Received: by 10.194.7.97 with SMTP id i1mr7174206wja.107.1430389269086; Thu, 30 Apr 2015 03:21:09 -0700 (PDT) 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 dq4sm1758925wid.17.2015.04.30.03.21.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 03:21:08 -0700 (PDT) From: Thomas Gazagnaire Message-Id: Date: Thu, 30 Apr 2015 11:21:07 +0100 To: Mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] fixing a memory leak in the tcp/ip stack 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 all, I've just released mirage-tcpip 2.4.2 (available in opam) which fixes a bad memory leak in the Channel implementation of tcpip/ip (thanks to Mindy Preston for the initial patches[1]). I've also added some memory statistics to mirage-www (in http://openmirage.org/stats/gc [2]) to check that the leak is indeed fixed. Can someone update the live website with the latest version of mirage-tcpip and mirage-www? Best, Thomas [1] https://github.com/mirage/mirage-tcpip/pull/127 [2] https://github.com/mirage/mirage-www/blob/master/src/stats.ml _______________________________________________ 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 Apr 30 10:21:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 10:21: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 1Ynlai-0006xu-7D; Thu, 30 Apr 2015 10:21:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ynlah-0006xl-74 for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 10:21:11 +0000 Received: from [193.109.254.147] by server-2.bemta-14.messagelabs.com id F6/9F-14319-61202455; Thu, 30 Apr 2015 10:21:10 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1430389269!13537920!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13063 invoked from network); 30 Apr 2015 10:21:09 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 10:21:09 -0000 Received: by widdi4 with SMTP id di4so13305293wid.0 for ; Thu, 30 Apr 2015 03:21:09 -0700 (PDT) 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=FIuGGTavN0EsXSJL/bPeAsfRHLXTUZUZSK/Hgu3J+7I=; b=hl0gvfIcQVno5o/gQIidx7ErXukeOUBkkO/6RW7YKhQp1IVY47S9TiSwqZgMGGpFOy uV3xTVGdmXfm2FNE8rV5kFiAiqL6HiPcGjT7lsAMK7g3H8N6N5NPqtIF/e2+UsEyE+oe Miv/b/jjLJwXgqESpiQUsRzFJ5GfrkCSSjHBhZegBaVYQTinSf5IUgKf5SxeaW9sjxD5 aUQFi850c/nIdx5SEj+K0so6g68yuNFRLZyeo20e8VtcHREuTDyO+A2kMDoONs5/x76T /ueOsIFJ9mR9D6UKRmR6HzuMN1HmI97Pqgi/T7zbR0LdqhLbTa0ZSH2dP6Z4CDBSamOF kl8w== X-Received: by 10.194.7.97 with SMTP id i1mr7174206wja.107.1430389269086; Thu, 30 Apr 2015 03:21:09 -0700 (PDT) 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 dq4sm1758925wid.17.2015.04.30.03.21.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 03:21:08 -0700 (PDT) From: Thomas Gazagnaire Message-Id: Date: Thu, 30 Apr 2015 11:21:07 +0100 To: Mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] fixing a memory leak in the tcp/ip stack 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 all, I've just released mirage-tcpip 2.4.2 (available in opam) which fixes a bad memory leak in the Channel implementation of tcpip/ip (thanks to Mindy Preston for the initial patches[1]). I've also added some memory statistics to mirage-www (in http://openmirage.org/stats/gc [2]) to check that the leak is indeed fixed. Can someone update the live website with the latest version of mirage-tcpip and mirage-www? Best, Thomas [1] https://github.com/mirage/mirage-tcpip/pull/127 [2] https://github.com/mirage/mirage-www/blob/master/src/stats.ml _______________________________________________ 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 Apr 30 11:29:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 11:29: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 1YnmeU-0001a8-An; Thu, 30 Apr 2015 11:29:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnmeT-0001a2-Qe for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 11:29:09 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 97/AB-12069-40212455; Thu, 30 Apr 2015 11:29:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1430393347!11304167!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16587 invoked from network); 30 Apr 2015 11:29:08 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 11:29:08 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 931a1feb; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 30 Apr 2015 12:29:07 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 30 Apr 2015 12:29:06 +0100 Message-Id: References: To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2098) Cc: Mirageos-devel Subject: Re: [MirageOS-devel] fixing a memory leak in the tcp/ip stack 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 Thanks Mindy and Thomas! The live openmirage.org website has picked this up. I've also (as discussed on the Mirage calls) set up a mirror of the site on http://mirage.io. This is intended to run the bleeding edge version of the stack and will be TLS-only, so don't link to it externally just yet. -anil > On 30 Apr 2015, at 11:21, Thomas Gazagnaire wrote: > > Hi all, > > I've just released mirage-tcpip 2.4.2 (available in opam) which fixes a bad memory leak in the Channel implementation of tcpip/ip (thanks to Mindy Preston for the initial patches[1]). I've also added some memory statistics to mirage-www (in http://openmirage.org/stats/gc [2]) to check that the leak is indeed fixed. > > Can someone update the live website with the latest version of mirage-tcpip and mirage-www? > > Best, > Thomas > > [1] https://github.com/mirage/mirage-tcpip/pull/127 > [2] https://github.com/mirage/mirage-www/blob/master/src/stats.ml > _______________________________________________ > 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 Thu Apr 30 11:29:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 11:29: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 1YnmeU-0001a8-An; Thu, 30 Apr 2015 11:29:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnmeT-0001a2-Qe for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 11:29:09 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 97/AB-12069-40212455; Thu, 30 Apr 2015 11:29:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1430393347!11304167!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16587 invoked from network); 30 Apr 2015 11:29:08 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 11:29:08 -0000 Received: from flick.office (volstagg-0.srg.cl.cam.ac.uk [128.232.32.232]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 931a1feb; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 30 Apr 2015 12:29:07 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 30 Apr 2015 12:29:06 +0100 Message-Id: References: To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2098) Cc: Mirageos-devel Subject: Re: [MirageOS-devel] fixing a memory leak in the tcp/ip stack 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 Thanks Mindy and Thomas! The live openmirage.org website has picked this up. I've also (as discussed on the Mirage calls) set up a mirror of the site on http://mirage.io. This is intended to run the bleeding edge version of the stack and will be TLS-only, so don't link to it externally just yet. -anil > On 30 Apr 2015, at 11:21, Thomas Gazagnaire wrote: > > Hi all, > > I've just released mirage-tcpip 2.4.2 (available in opam) which fixes a bad memory leak in the Channel implementation of tcpip/ip (thanks to Mindy Preston for the initial patches[1]). I've also added some memory statistics to mirage-www (in http://openmirage.org/stats/gc [2]) to check that the leak is indeed fixed. > > Can someone update the live website with the latest version of mirage-tcpip and mirage-www? > > Best, > Thomas > > [1] https://github.com/mirage/mirage-tcpip/pull/127 > [2] https://github.com/mirage/mirage-www/blob/master/src/stats.ml > _______________________________________________ > 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 Thu Apr 30 15:01:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 15:01: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 1YnpyK-0000pe-UZ; Thu, 30 Apr 2015 15:01:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnpyJ-0000pZ-L2 for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 15:01:51 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 51/E5-20070-ED342455; Thu, 30 Apr 2015 15:01:50 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1430406110!11882146!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8622 invoked from network); 30 Apr 2015 15:01:50 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 15:01:50 -0000 Received: by wicmx19 with SMTP id mx19so15239543wic.1 for ; Thu, 30 Apr 2015 08:01:49 -0700 (PDT) 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=SB92s/0kMeQrI27WmZQ7MFSDT2541gvucGHPd5KNn4E=; b=NhsmsMiCWMkzkmlzJMrVfCxoBbQJfvEb+ch8JazwstQWSh+z/sQi1Ys7zoDPBZ03Z9 Wz4djanm5Mbtu80safDMydTO09u+LoCOkgk2Tq2TaFbmQMhQszT9gytVhlyjBgwrNp3A 61cDH2QcUcojEnlKqMx2PWbCWavzdFY5dJq1nA0SRGR5bzGqYSfMJ+vPzNng9xGrNfap nFJhyilOTwqsEHfa2IqTLUG+XnLgeS2v3dJA+VxVHLjV27g85zPi6RkrOzn0G5B+HtIM llKJMtH64Fcq80xMQa6ORKAvET+6GymgSrFFIiD8kr+zNNr5L5f3bOasxroIVj7YWDvL qj/g== X-Received: by 10.180.206.229 with SMTP id lr5mr6439435wic.86.1430406109768; Thu, 30 Apr 2015 08:01:49 -0700 (PDT) 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 di9sm2824249wib.16.2015.04.30.08.01.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 08:01:48 -0700 (PDT) From: Thomas Gazagnaire Message-Id: <099503D4-981F-4BBC-B463-7F513330B3A9@gazagnaire.org> Date: Thu, 30 Apr 2015 16:01:47 +0100 To: Mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] call for reviewers for mirage-tcpip 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 all, I am looking for volunteers to help me review patches over the mirage-tcpip code: https://github.com/mirage/mirage-tcpip/pull/130 Any kind of feedback will be kindly appreciated, especially regarding the update of the ARP tables and the filtering of source IP address. Best, 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 Apr 30 15:01:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 15:01: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 1YnpyK-0000pe-UZ; Thu, 30 Apr 2015 15:01:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnpyJ-0000pZ-L2 for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 15:01:51 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 51/E5-20070-ED342455; Thu, 30 Apr 2015 15:01:50 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1430406110!11882146!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8622 invoked from network); 30 Apr 2015 15:01:50 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 15:01:50 -0000 Received: by wicmx19 with SMTP id mx19so15239543wic.1 for ; Thu, 30 Apr 2015 08:01:49 -0700 (PDT) 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=SB92s/0kMeQrI27WmZQ7MFSDT2541gvucGHPd5KNn4E=; b=NhsmsMiCWMkzkmlzJMrVfCxoBbQJfvEb+ch8JazwstQWSh+z/sQi1Ys7zoDPBZ03Z9 Wz4djanm5Mbtu80safDMydTO09u+LoCOkgk2Tq2TaFbmQMhQszT9gytVhlyjBgwrNp3A 61cDH2QcUcojEnlKqMx2PWbCWavzdFY5dJq1nA0SRGR5bzGqYSfMJ+vPzNng9xGrNfap nFJhyilOTwqsEHfa2IqTLUG+XnLgeS2v3dJA+VxVHLjV27g85zPi6RkrOzn0G5B+HtIM llKJMtH64Fcq80xMQa6ORKAvET+6GymgSrFFIiD8kr+zNNr5L5f3bOasxroIVj7YWDvL qj/g== X-Received: by 10.180.206.229 with SMTP id lr5mr6439435wic.86.1430406109768; Thu, 30 Apr 2015 08:01:49 -0700 (PDT) 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 di9sm2824249wib.16.2015.04.30.08.01.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 08:01:48 -0700 (PDT) From: Thomas Gazagnaire Message-Id: <099503D4-981F-4BBC-B463-7F513330B3A9@gazagnaire.org> Date: Thu, 30 Apr 2015 16:01:47 +0100 To: Mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] call for reviewers for mirage-tcpip 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 all, I am looking for volunteers to help me review patches over the mirage-tcpip code: https://github.com/mirage/mirage-tcpip/pull/130 Any kind of feedback will be kindly appreciated, especially regarding the update of the ARP tables and the filtering of source IP address. Best, 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 Apr 30 15:16:27 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 15:16: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 1YnqCP-0001Yr-M7; Thu, 30 Apr 2015 15:16:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnqCO-0001YY-6q for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 15:16:24 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id E6/7F-09361-74742455; Thu, 30 Apr 2015 15:16:23 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-8.tower-31.messagelabs.com!1430406981!11402099!1 X-Originating-IP: [66.111.4.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTExLjQuMjUgPT4gNDQ5ODE=\n X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16843 invoked from network); 30 Apr 2015 15:16:22 -0000 Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 15:16:22 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A567C20BE2 for ; Thu, 30 Apr 2015 11:16:21 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Thu, 30 Apr 2015 11:16:21 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=koW 8NBRJNCrtXuG4wHTafIkZ2rk=; b=I3V9xQxEctL/pzN73hkh8IQmtBxValUI+m8 AjivE38WX8EA8XzixCw01sTCFyCkBkXGJpWYdl+/7bZPjb/DffQPxGdnaHsvVO1w TgNxZJZmbzq6uFJ3TLlnCobAxdwXJ7tf8B683RauwDFi8YqwFlEA/Y0XcrIAnQHr nKMhqys0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=koW8NBRJNCrtXuG4wHTafIkZ2rk=; b=tIgQy trZueTT41AdAKPtDMBqiC/M9J1mYGubwMLyLrkJCnPkJrBjvC/Tdk34RhR4KhBKq rQyirOd2M0ULjjD2954DNZZIP5R+ayU2k9pFwN3S1BhoOnhs2oDW4zGHHGRZz67O 1zCNAgP4BZiO3Q8652xDhVrulENemmyJVTAyfc= Received: by web2.nyi.internal (Postfix, from userid 99) id 7040A54006C; Thu, 30 Apr 2015 11:16:21 -0400 (EDT) Message-Id: <1430406981.545751.260957069.2EE73E91@webmail.messagingengine.com> X-Sasl-Enc: PtAhpjFlm/UtOBZh8n+0liV+kYSKN/2uKPO93khFATvP 1430406981 From: Magnus Skjegstad To: mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-f5f4dd6c Date: Thu, 30 Apr 2015 17:16:21 +0200 Subject: [MirageOS-devel] Mirage-vnetif v0.1 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 Mirage-vnetif is a virtual network interface and software bridge for Mirage. It can be used to run client/server network tests from a single unikernel. https://github.com/MagnusS/mirage-vnetif A quick introduction is available in the README: https://github.com/MagnusS/mirage-vnetif/blob/master/README.md A few example unikernels are also available here: https://github.com/MagnusS/mirage-vnetif/tree/master/examples -- Magnus _______________________________________________ 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 Apr 30 15:16:27 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 15:16: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 1YnqCP-0001Yr-M7; Thu, 30 Apr 2015 15:16:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnqCO-0001YY-6q for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 15:16:24 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id E6/7F-09361-74742455; Thu, 30 Apr 2015 15:16:23 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-8.tower-31.messagelabs.com!1430406981!11402099!1 X-Originating-IP: [66.111.4.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTExLjQuMjUgPT4gNDQ5ODE=\n X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16843 invoked from network); 30 Apr 2015 15:16:22 -0000 Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 15:16:22 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A567C20BE2 for ; Thu, 30 Apr 2015 11:16:21 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Thu, 30 Apr 2015 11:16:21 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=koW 8NBRJNCrtXuG4wHTafIkZ2rk=; b=I3V9xQxEctL/pzN73hkh8IQmtBxValUI+m8 AjivE38WX8EA8XzixCw01sTCFyCkBkXGJpWYdl+/7bZPjb/DffQPxGdnaHsvVO1w TgNxZJZmbzq6uFJ3TLlnCobAxdwXJ7tf8B683RauwDFi8YqwFlEA/Y0XcrIAnQHr nKMhqys0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=koW8NBRJNCrtXuG4wHTafIkZ2rk=; b=tIgQy trZueTT41AdAKPtDMBqiC/M9J1mYGubwMLyLrkJCnPkJrBjvC/Tdk34RhR4KhBKq rQyirOd2M0ULjjD2954DNZZIP5R+ayU2k9pFwN3S1BhoOnhs2oDW4zGHHGRZz67O 1zCNAgP4BZiO3Q8652xDhVrulENemmyJVTAyfc= Received: by web2.nyi.internal (Postfix, from userid 99) id 7040A54006C; Thu, 30 Apr 2015 11:16:21 -0400 (EDT) Message-Id: <1430406981.545751.260957069.2EE73E91@webmail.messagingengine.com> X-Sasl-Enc: PtAhpjFlm/UtOBZh8n+0liV+kYSKN/2uKPO93khFATvP 1430406981 From: Magnus Skjegstad To: mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-f5f4dd6c Date: Thu, 30 Apr 2015 17:16:21 +0200 Subject: [MirageOS-devel] Mirage-vnetif v0.1 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 Mirage-vnetif is a virtual network interface and software bridge for Mirage. It can be used to run client/server network tests from a single unikernel. https://github.com/MagnusS/mirage-vnetif A quick introduction is available in the README: https://github.com/MagnusS/mirage-vnetif/blob/master/README.md A few example unikernels are also available here: https://github.com/MagnusS/mirage-vnetif/tree/master/examples -- Magnus _______________________________________________ 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 Apr 30 15:26:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 15:26:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnqMS-0001s5-GX; Thu, 30 Apr 2015 15:26:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnqMR-0001s0-CZ for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 15:26:47 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id A6/DE-23555-6B942455; Thu, 30 Apr 2015 15:26:46 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1430407605!11405811!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14034 invoked from network); 30 Apr 2015 15:26:45 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 15:26:45 -0000 Received: by wizk4 with SMTP id k4so24129882wiz.1 for ; Thu, 30 Apr 2015 08:26:45 -0700 (PDT) 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=SP76oUXGyjJsrkiqbZVq99lEg8npi0m71nLLENQW3DY=; b=l4CTV6U9O5lTVXAapaPaaN4rLzGbslkLhwvgGBilPI7LR2HqZsNa0zSPAFJXxK+jSL cWgLbCzk6iuB2wJXh0c2QHrcq2yVWjOc4zJiQzHGqK14RF2yf4ZGhqWn5XGLxK8IyY6L U+I3gHP6GYM4rGXoPpMPeQzgkAK2zVH3plz+Bs5inajOx58kr4bvnyt3TsfTBChk0Y4h Hw7604BJiDwlf9SV4Si0PtGx/fD+cVnYZ4xBaM/yXwxhptBBPJErTu9eoOuJRSjer+8V wockrNltMWHEn5rFAlzuw9YsJXSoSqw1Dj3l7yUptDEcWnIUZTcOy0ic9g2RNIrYgwIX F8Lg== X-Received: by 10.180.20.200 with SMTP id p8mr6425002wie.78.1430407605018; Thu, 30 Apr 2015 08:26:45 -0700 (PDT) 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 l20sm3748104wjw.42.2015.04.30.08.26.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 08:26:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: <1430406981.545751.260957069.2EE73E91@webmail.messagingengine.com> Date: Thu, 30 Apr 2015 16:26:42 +0100 Message-Id: <0E868BDD-2348-4B12-B755-761F33E868EC@gazagnaire.org> References: <1430406981.545751.260957069.2EE73E91@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-vnetif v0.1 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 Cool! I've created a pull request[1] to make it available in opam using opam-publish: $ opam-publish prepare mirage-vnetif.0.1.0 https://github.com/MagnusS/mirage-vnetif/archive/0.1.tar.gz [ ... edit mirage-vnetif.0.1.0/descr ... ] $ opam-publish submit ./mirage-vnetif.0.1.0 Best, Thomas [1] https://github.com/ocaml/opam-repository/pull/4034 > On 30 Apr 2015, at 16:16, Magnus Skjegstad wrote: > > Mirage-vnetif is a virtual network interface and software bridge for > Mirage. It can be used to run client/server network tests from a single > unikernel. > > https://github.com/MagnusS/mirage-vnetif > > A quick introduction is available in the README: > https://github.com/MagnusS/mirage-vnetif/blob/master/README.md > > A few example unikernels are also available here: > https://github.com/MagnusS/mirage-vnetif/tree/master/examples > > -- > Magnus > > _______________________________________________ > 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 Thu Apr 30 15:26:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 15:26:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnqMS-0001s5-GX; Thu, 30 Apr 2015 15:26:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnqMR-0001s0-CZ for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 15:26:47 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id A6/DE-23555-6B942455; Thu, 30 Apr 2015 15:26:46 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1430407605!11405811!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14034 invoked from network); 30 Apr 2015 15:26:45 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 15:26:45 -0000 Received: by wizk4 with SMTP id k4so24129882wiz.1 for ; Thu, 30 Apr 2015 08:26:45 -0700 (PDT) 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=SP76oUXGyjJsrkiqbZVq99lEg8npi0m71nLLENQW3DY=; b=l4CTV6U9O5lTVXAapaPaaN4rLzGbslkLhwvgGBilPI7LR2HqZsNa0zSPAFJXxK+jSL cWgLbCzk6iuB2wJXh0c2QHrcq2yVWjOc4zJiQzHGqK14RF2yf4ZGhqWn5XGLxK8IyY6L U+I3gHP6GYM4rGXoPpMPeQzgkAK2zVH3plz+Bs5inajOx58kr4bvnyt3TsfTBChk0Y4h Hw7604BJiDwlf9SV4Si0PtGx/fD+cVnYZ4xBaM/yXwxhptBBPJErTu9eoOuJRSjer+8V wockrNltMWHEn5rFAlzuw9YsJXSoSqw1Dj3l7yUptDEcWnIUZTcOy0ic9g2RNIrYgwIX F8Lg== X-Received: by 10.180.20.200 with SMTP id p8mr6425002wie.78.1430407605018; Thu, 30 Apr 2015 08:26:45 -0700 (PDT) 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 l20sm3748104wjw.42.2015.04.30.08.26.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 08:26:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: <1430406981.545751.260957069.2EE73E91@webmail.messagingengine.com> Date: Thu, 30 Apr 2015 16:26:42 +0100 Message-Id: <0E868BDD-2348-4B12-B755-761F33E868EC@gazagnaire.org> References: <1430406981.545751.260957069.2EE73E91@webmail.messagingengine.com> To: Magnus Skjegstad X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-vnetif v0.1 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 Cool! I've created a pull request[1] to make it available in opam using opam-publish: $ opam-publish prepare mirage-vnetif.0.1.0 https://github.com/MagnusS/mirage-vnetif/archive/0.1.tar.gz [ ... edit mirage-vnetif.0.1.0/descr ... ] $ opam-publish submit ./mirage-vnetif.0.1.0 Best, Thomas [1] https://github.com/ocaml/opam-repository/pull/4034 > On 30 Apr 2015, at 16:16, Magnus Skjegstad wrote: > > Mirage-vnetif is a virtual network interface and software bridge for > Mirage. It can be used to run client/server network tests from a single > unikernel. > > https://github.com/MagnusS/mirage-vnetif > > A quick introduction is available in the README: > https://github.com/MagnusS/mirage-vnetif/blob/master/README.md > > A few example unikernels are also available here: > https://github.com/MagnusS/mirage-vnetif/tree/master/examples > > -- > Magnus > > _______________________________________________ > 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 Thu Apr 30 17:16:17 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 17:16: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 1Yns4J-0007ho-HQ; Thu, 30 Apr 2015 17:16:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yns4J-0007hh-7h for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 17:16:11 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id 17/76-24420-95362455; Thu, 30 Apr 2015 17:16:09 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-9.tower-27.messagelabs.com!1430414169!13690814!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20778 invoked from network); 30 Apr 2015 17:16:09 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 17:16:09 -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]:57756 helo=[192.168.0.8]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpsa (PLAIN:amc79) (TLSv1:DHE-RSA-AES256-SHA:256) id 1Yns4G-0002MN-sE (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 30 Apr 2015 18:16:08 +0100 From: Amir Chaudhry Message-Id: Date: Thu, 30 Apr 2015 18:16:08 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] Jitsu and Networking status - next steps 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, It would be good to get an update of where things stand with both Jitsu and the TCP stack. ThomasG, I believe you have a task list? Could you share it here? 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 Thu Apr 30 17:16:17 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 17:16: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 1Yns4J-0007ho-HQ; Thu, 30 Apr 2015 17:16:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yns4J-0007hh-7h for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 17:16:11 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id 17/76-24420-95362455; Thu, 30 Apr 2015 17:16:09 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-9.tower-27.messagelabs.com!1430414169!13690814!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20778 invoked from network); 30 Apr 2015 17:16:09 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2015 17:16:09 -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]:57756 helo=[192.168.0.8]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpsa (PLAIN:amc79) (TLSv1:DHE-RSA-AES256-SHA:256) id 1Yns4G-0002MN-sE (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 30 Apr 2015 18:16:08 +0100 From: Amir Chaudhry Message-Id: Date: Thu, 30 Apr 2015 18:16:08 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Subject: [MirageOS-devel] Jitsu and Networking status - next steps 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, It would be good to get an update of where things stand with both Jitsu and the TCP stack. ThomasG, I believe you have a task list? Could you share it here? 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 Thu Apr 30 17:31:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 17:31: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 1YnsIy-0008Lw-2f; Thu, 30 Apr 2015 17:31:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnsIx-0008Lq-DN for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 17:31:19 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id 17/16-25404-6E662455; Thu, 30 Apr 2015 17:31:18 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1430415072!7816111!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4241 invoked from network); 30 Apr 2015 17:31:12 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 17:31:12 -0000 Received: by wgyo15 with SMTP id o15so70193753wgy.2 for ; Thu, 30 Apr 2015 10:31:12 -0700 (PDT) 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=I45qMLbwZKdi1ztsx53TGJN6MPf+oE0p4cUDN7xEvcs=; b=h1gzLjQ+jp0OFGMf10h9Gg2u74/Y1+m+BDdHR77Ku3FfByzfOigfMrfSjndi2bsHZW aOoBlsmiYufm6EvV5Zd5GgTX8IaRGpQNlhshCWfAwNOU65DKbK4AgiGIC2Fb2qpB5M75 WpXBRWWYQKcTDQPGswjF6CkvD1Ch4JbnqmtrzfwvqgoGSEw3pWC4xlJVfjXXWkvCgwMj a/wf/AI23U0/ybCpmSZbutVCG+D1MOHL+eBt5qcmDhnkx8Wx73vqp7tYld+OU6+Fzocu sEuR8/mL9rL9b1YVOZsjp/Zk0sKmupHzO8TWeGd+lbPyZx/RnSAM9QhT5ffyilUIjqgc nFbQ== X-Received: by 10.180.88.8 with SMTP id bc8mr7362524wib.19.1430415072069; Thu, 30 Apr 2015 10:31:12 -0700 (PDT) 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 q4sm4199507wja.24.2015.04.30.10.31.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 10:31:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 30 Apr 2015 18:31:09 +0100 Message-Id: <1D7C52AB-2A00-4FAE-91D9-305FCC046B9F@gazagnaire.org> References: To: Amir Chaudhry X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Jitsu and Networking status - next steps 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 > It would be good to get an update of where things stand with both Jitsu and the TCP stack. ThomasG, I believe you have a task list? Could you share it here? I've created https://github.com/mirage/jitsu/issues/11 to track that. Summary: we need more tests and eyeballs. Best, 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 Apr 30 17:31:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 17:31: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 1YnsIy-0008Lw-2f; Thu, 30 Apr 2015 17:31:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnsIx-0008Lq-DN for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 17:31:19 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id 17/16-25404-6E662455; Thu, 30 Apr 2015 17:31:18 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1430415072!7816111!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4241 invoked from network); 30 Apr 2015 17:31:12 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 17:31:12 -0000 Received: by wgyo15 with SMTP id o15so70193753wgy.2 for ; Thu, 30 Apr 2015 10:31:12 -0700 (PDT) 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=I45qMLbwZKdi1ztsx53TGJN6MPf+oE0p4cUDN7xEvcs=; b=h1gzLjQ+jp0OFGMf10h9Gg2u74/Y1+m+BDdHR77Ku3FfByzfOigfMrfSjndi2bsHZW aOoBlsmiYufm6EvV5Zd5GgTX8IaRGpQNlhshCWfAwNOU65DKbK4AgiGIC2Fb2qpB5M75 WpXBRWWYQKcTDQPGswjF6CkvD1Ch4JbnqmtrzfwvqgoGSEw3pWC4xlJVfjXXWkvCgwMj a/wf/AI23U0/ybCpmSZbutVCG+D1MOHL+eBt5qcmDhnkx8Wx73vqp7tYld+OU6+Fzocu sEuR8/mL9rL9b1YVOZsjp/Zk0sKmupHzO8TWeGd+lbPyZx/RnSAM9QhT5ffyilUIjqgc nFbQ== X-Received: by 10.180.88.8 with SMTP id bc8mr7362524wib.19.1430415072069; Thu, 30 Apr 2015 10:31:12 -0700 (PDT) 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 q4sm4199507wja.24.2015.04.30.10.31.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Apr 2015 10:31:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 30 Apr 2015 18:31:09 +0100 Message-Id: <1D7C52AB-2A00-4FAE-91D9-305FCC046B9F@gazagnaire.org> References: To: Amir Chaudhry X-Mailer: Apple Mail (2.2098) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Jitsu and Networking status - next steps 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 > It would be good to get an update of where things stand with both Jitsu and the TCP stack. ThomasG, I believe you have a task list? Could you share it here? I've created https://github.com/mirage/jitsu/issues/11 to track that. Summary: we need more tests and eyeballs. Best, 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 Apr 30 21:56:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 21:56:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnwR8-00083J-HB; Thu, 30 Apr 2015 21:56:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnwR6-00083E-4d for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 21:56:00 +0000 Received: from [193.109.254.147] by server-7.bemta-14.messagelabs.com id 08/28-03770-FE4A2455; Thu, 30 Apr 2015 21:55:59 +0000 X-Env-Sender: robertream@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1430430958!8343657!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9880 invoked from network); 30 Apr 2015 21:55:58 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 21:55:58 -0000 Received: by wiun10 with SMTP id n10so32810404wiu.1 for ; Thu, 30 Apr 2015 14:55:58 -0700 (PDT) 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=MTOy8Xm6K5tv4UV2DUxv19EWJE+AnN0+GwFu4YOmP4A=; b=CJzLJ1q4U4qFM4zZv5swNAtRLfJ4oOj1yADh5TI/2JkBApHX1rX/e7tW6HDTjDeOi1 Vb68j9YOc8W0soJhv8WauTnEeE0ReH+Q+PJk7wIHS4KxCTqa/YrlN0rnr8vUKYNRmZ/I JqwGc7SL/idheV8J5goipHlN2J3Cw/G2X5bB+b6AfJaNsj6wszESCDwurrzOfVDnjoyX Rh1HutpK5D0KT4xb4NWqbpAvc1WfsunaORGN2ow+wbrW/KYhmiKRcXJxbSROY8oh3PEg 4XKu26Cyo9VZ4sutgdd12BcP4fFHLFd4tK52WUhLio2E8Rds6S4nXeAl0dRXXlftcbKq XnBw== MIME-Version: 1.0 X-Received: by 10.194.204.230 with SMTP id lb6mr12240433wjc.63.1430430957960; Thu, 30 Apr 2015 14:55:57 -0700 (PDT) Received: by 10.194.162.197 with HTTP; Thu, 30 Apr 2015 14:55:57 -0700 (PDT) Date: Thu, 30 Apr 2015 14:55:57 -0700 Message-ID: From: Robert Ream To: mirageos-devel Subject: [MirageOS-devel] mirage-net-unix 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: multipart/mixed; boundary="===============0197989727852130584==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0197989727852130584== Content-Type: multipart/alternative; boundary=047d7b8738a22004210514f8290e --047d7b8738a22004210514f8290e Content-Type: text/plain; charset=UTF-8 Ok, I'm still stumped. Two things happen with pretty much all of the network examples when I build and execute them for unix: 1) they promptly exit with a "Netif: error, terminating listen loop" and 2) tun0 disappears and must be recreated every time. 1) I tracked down the lines of code in mirage-net-unix that cause this error message: let page = Io_page.get 1 in read t page >>= function | `Error _ -> printf "Netif: error, terminating listen loop\n%!"; return () So it is running into an error when reading a page from the network. It would be nice to pretty print the _ of `Error _ instead of drop it on the floor. 2) I couldn't find anywhere in the code that remotely appeared to be messing with or deleting the tun0 interface. But I wonder if the error I'm seeing is due to the tun0 disappearing? -Robert --047d7b8738a22004210514f8290e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ok, I'm stil= l stumped.

Two things happen with pretty much all of the netwo= rk examples when I build and execute them for unix: 1) they promptly exit w= ith a "Netif: error, terminating listen loop" and 2) tun0 disappe= ars and must be recreated every time.

1) I tracked down the lines of code in mirage-net-unix that c= ause this error message:

let page = =3D = Io_page.get 1 in read t= page >= >=3D function | `Error _ -> = printf "Netif: error, terminat= ing listen loop\n%!<= span class=3D"">"; = return ()

<= span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm= all;line-height:normal;white-space:normal">So it is running into an error w= hen reading a page from the network.
It = would be nice to pretty print the _ of `Error _ instead of drop it on the f= loor.

2) I couldn't = find anywhere in the code that remotely appeared to be messing with or dele= ting the tun0 interface. But I wonder if the error I'm seeing is due to= the tun0 disappearing?

<= /span>
-Robert
--047d7b8738a22004210514f8290e-- --===============0197989727852130584== 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 --===============0197989727852130584==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 21:56:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 21:56:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnwR8-00083J-HB; Thu, 30 Apr 2015 21:56:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnwR6-00083E-4d for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 21:56:00 +0000 Received: from [193.109.254.147] by server-7.bemta-14.messagelabs.com id 08/28-03770-FE4A2455; Thu, 30 Apr 2015 21:55:59 +0000 X-Env-Sender: robertream@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1430430958!8343657!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9880 invoked from network); 30 Apr 2015 21:55:58 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 21:55:58 -0000 Received: by wiun10 with SMTP id n10so32810404wiu.1 for ; Thu, 30 Apr 2015 14:55:58 -0700 (PDT) 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=MTOy8Xm6K5tv4UV2DUxv19EWJE+AnN0+GwFu4YOmP4A=; b=CJzLJ1q4U4qFM4zZv5swNAtRLfJ4oOj1yADh5TI/2JkBApHX1rX/e7tW6HDTjDeOi1 Vb68j9YOc8W0soJhv8WauTnEeE0ReH+Q+PJk7wIHS4KxCTqa/YrlN0rnr8vUKYNRmZ/I JqwGc7SL/idheV8J5goipHlN2J3Cw/G2X5bB+b6AfJaNsj6wszESCDwurrzOfVDnjoyX Rh1HutpK5D0KT4xb4NWqbpAvc1WfsunaORGN2ow+wbrW/KYhmiKRcXJxbSROY8oh3PEg 4XKu26Cyo9VZ4sutgdd12BcP4fFHLFd4tK52WUhLio2E8Rds6S4nXeAl0dRXXlftcbKq XnBw== MIME-Version: 1.0 X-Received: by 10.194.204.230 with SMTP id lb6mr12240433wjc.63.1430430957960; Thu, 30 Apr 2015 14:55:57 -0700 (PDT) Received: by 10.194.162.197 with HTTP; Thu, 30 Apr 2015 14:55:57 -0700 (PDT) Date: Thu, 30 Apr 2015 14:55:57 -0700 Message-ID: From: Robert Ream To: mirageos-devel Subject: [MirageOS-devel] mirage-net-unix 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: multipart/mixed; boundary="===============0197989727852130584==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0197989727852130584== Content-Type: multipart/alternative; boundary=047d7b8738a22004210514f8290e --047d7b8738a22004210514f8290e Content-Type: text/plain; charset=UTF-8 Ok, I'm still stumped. Two things happen with pretty much all of the network examples when I build and execute them for unix: 1) they promptly exit with a "Netif: error, terminating listen loop" and 2) tun0 disappears and must be recreated every time. 1) I tracked down the lines of code in mirage-net-unix that cause this error message: let page = Io_page.get 1 in read t page >>= function | `Error _ -> printf "Netif: error, terminating listen loop\n%!"; return () So it is running into an error when reading a page from the network. It would be nice to pretty print the _ of `Error _ instead of drop it on the floor. 2) I couldn't find anywhere in the code that remotely appeared to be messing with or deleting the tun0 interface. But I wonder if the error I'm seeing is due to the tun0 disappearing? -Robert --047d7b8738a22004210514f8290e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ok, I'm stil= l stumped.

Two things happen with pretty much all of the netwo= rk examples when I build and execute them for unix: 1) they promptly exit w= ith a "Netif: error, terminating listen loop" and 2) tun0 disappe= ars and must be recreated every time.

1) I tracked down the lines of code in mirage-net-unix that c= ause this error message:

let page = =3D = Io_page.get 1 in read t= page >= >=3D function | `Error _ -> = printf "Netif: error, terminat= ing listen loop\n%!<= span class=3D"">"; = return ()

<= span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm= all;line-height:normal;white-space:normal">So it is running into an error w= hen reading a page from the network.
It = would be nice to pretty print the _ of `Error _ instead of drop it on the f= loor.

2) I couldn't = find anywhere in the code that remotely appeared to be messing with or dele= ting the tun0 interface. But I wonder if the error I'm seeing is due to= the tun0 disappearing?

<= /span>
-Robert
--047d7b8738a22004210514f8290e-- --===============0197989727852130584== 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 --===============0197989727852130584==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 22:49:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 22:49: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 1YnxGW-0001NY-Ha; Thu, 30 Apr 2015 22:49:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnxGV-0001M0-2H for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 22:49:07 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id ED/25-29354-261B2455; Thu, 30 Apr 2015 22:49:06 +0000 X-Env-Sender: robertream@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1430434144!11975133!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26786 invoked from network); 30 Apr 2015 22:49:05 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 22:49:05 -0000 Received: by widdi4 with SMTP id di4so36658639wid.0 for ; Thu, 30 Apr 2015 15:49:04 -0700 (PDT) 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 :content-type; bh=aMQyWzR0vc6xqYG+CJ5DsKj2pQeUSXCnrCre6z0wCzw=; b=X+ut2eSn0U6PM/4s905I579MTmdQ6s6efJNnQBrgwJXhqgUSW+Q/0Ii00wkHutWv2C D2fdkS9IBgP45x3DoyBKRpjpSPcReS9x09dQwEKJVqFmAkorb0OmBzDgL949Laa2sWD2 z1X/OOHudh4eP1phltRqHV0w/bwuXtwBUFTJQfGLGXi4AEujz01RzKc0a3O3rDPXeRtm 9sKUsOPsR0dA8tZcT+EftbOgfKQhstp1poshFXxgTAJwb49wSKd7k4ZufGlpW422x5p/ QqceyAQGUbT/us7GvU4ZRBXYTQ70Pq8D/dMPx5s8VBboPhF/Q8y0Bo4/iFuByBUPBAo5 2UkQ== MIME-Version: 1.0 X-Received: by 10.194.85.116 with SMTP id g20mr12830177wjz.154.1430434144610; Thu, 30 Apr 2015 15:49:04 -0700 (PDT) Received: by 10.194.162.197 with HTTP; Thu, 30 Apr 2015 15:49:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Apr 2015 15:49:04 -0700 Message-ID: From: Robert Ream To: mirageos-devel Subject: Re: [MirageOS-devel] mirage-net-unix 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: multipart/mixed; boundary="===============1394627386574588112==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1394627386574588112== Content-Type: multipart/alternative; boundary=047d7bfcfd50106f630514f8e769 --047d7bfcfd50106f630514f8e769 Content-Type: text/plain; charset=UTF-8 An update: I just cloned the mirage-net-unix repo and ran the tests. This is what I got: sudo ./test.native plugging into tap0 with mac c2:9d:56:19:d7:2c.. Netif: connect tap0 connected Netif: error, terminating listen loop . Ran: 1 tests in: 0.00 seconds. OK And the tun0 interface disappeared as well. On Thu, Apr 30, 2015 at 2:55 PM, Robert Ream wrote: > Ok, I'm still stumped. > > Two things happen with pretty much all of the network examples when I > build and execute them for unix: 1) they promptly exit with a "Netif: > error, terminating listen loop" and 2) tun0 disappears and must be > recreated every time. > > 1) I tracked down the lines of code in mirage-net-unix that cause this > error message: > > let page = Io_page.get 1 in read t page >>= function | `Error _ -> printf > "Netif: error, terminating listen loop\n%!"; return () > > So it is running into an error when reading a page from the network. > It would be nice to pretty print the _ of `Error _ instead of drop it on > the floor. > > 2) I couldn't find anywhere in the code that remotely appeared to be > messing with or deleting the tun0 interface. But I wonder if the error I'm > seeing is due to the tun0 disappearing? > > -Robert > --047d7bfcfd50106f630514f8e769 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
An update: I just cloned the mirage-net-unix repo and= ran the tests. This is what I got:

sudo ./test.native
plugging i= nto tap0 with mac c2:9d:56:19:d7:2c..
Netif: connect tap0
connectedNetif: error, terminating listen loop
.
Ran: 1 tests in: 0.00 secon= ds.
OK

And the tun0 interface disappeared as well.
=



On Thu, Apr 30, 2015 at 2:55 PM, Robert Ream <= robertream@gmail.com> wrote:
Ok, I'm st= ill stumped.

Two things happen with pretty much all of the net= work examples when I build and execute them for unix: 1) they promptly exit= with a "Netif: error, terminating listen loop" and 2) tun0 disap= pears and must be recreated every time.

1) I tracked down the lines of code in mirage-net-unix tha= t cause this error message:
let pag= e =3D Io_page.get 1 in read t= page >>= =3D function | `Error _<= span style=3D"color:rgb(51,51,51);line-height:18.2000007629395px"> -> = printf "Netif: error, terminating listen loop\n%!"; = return ()

=
So= it is running into an error when reading a page from the network.
It would be nice to pretty print the _ of `Error _ instead of dro= p it on the floor.

2) I couldn't find = anywhere in the code that remotely appeared to be messing with or deleting = the tun0 interface. But I wonder if the error I'm seeing is due to the = tun0 disappearing?
<= br>
-Robert

--047d7bfcfd50106f630514f8e769-- --===============1394627386574588112== 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 --===============1394627386574588112==-- From mirageos-devel-bounces@lists.xenproject.org Thu Apr 30 22:49:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 30 Apr 2015 22:49: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 1YnxGW-0001NY-Ha; Thu, 30 Apr 2015 22:49:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YnxGV-0001M0-2H for mirageos-devel@lists.xenproject.org; Thu, 30 Apr 2015 22:49:07 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id ED/25-29354-261B2455; Thu, 30 Apr 2015 22:49:06 +0000 X-Env-Sender: robertream@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1430434144!11975133!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26786 invoked from network); 30 Apr 2015 22:49:05 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2015 22:49:05 -0000 Received: by widdi4 with SMTP id di4so36658639wid.0 for ; Thu, 30 Apr 2015 15:49:04 -0700 (PDT) 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 :content-type; bh=aMQyWzR0vc6xqYG+CJ5DsKj2pQeUSXCnrCre6z0wCzw=; b=X+ut2eSn0U6PM/4s905I579MTmdQ6s6efJNnQBrgwJXhqgUSW+Q/0Ii00wkHutWv2C D2fdkS9IBgP45x3DoyBKRpjpSPcReS9x09dQwEKJVqFmAkorb0OmBzDgL949Laa2sWD2 z1X/OOHudh4eP1phltRqHV0w/bwuXtwBUFTJQfGLGXi4AEujz01RzKc0a3O3rDPXeRtm 9sKUsOPsR0dA8tZcT+EftbOgfKQhstp1poshFXxgTAJwb49wSKd7k4ZufGlpW422x5p/ QqceyAQGUbT/us7GvU4ZRBXYTQ70Pq8D/dMPx5s8VBboPhF/Q8y0Bo4/iFuByBUPBAo5 2UkQ== MIME-Version: 1.0 X-Received: by 10.194.85.116 with SMTP id g20mr12830177wjz.154.1430434144610; Thu, 30 Apr 2015 15:49:04 -0700 (PDT) Received: by 10.194.162.197 with HTTP; Thu, 30 Apr 2015 15:49:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Apr 2015 15:49:04 -0700 Message-ID: From: Robert Ream To: mirageos-devel Subject: Re: [MirageOS-devel] mirage-net-unix 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: multipart/mixed; boundary="===============1394627386574588112==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1394627386574588112== Content-Type: multipart/alternative; boundary=047d7bfcfd50106f630514f8e769 --047d7bfcfd50106f630514f8e769 Content-Type: text/plain; charset=UTF-8 An update: I just cloned the mirage-net-unix repo and ran the tests. This is what I got: sudo ./test.native plugging into tap0 with mac c2:9d:56:19:d7:2c.. Netif: connect tap0 connected Netif: error, terminating listen loop . Ran: 1 tests in: 0.00 seconds. OK And the tun0 interface disappeared as well. On Thu, Apr 30, 2015 at 2:55 PM, Robert Ream wrote: > Ok, I'm still stumped. > > Two things happen with pretty much all of the network examples when I > build and execute them for unix: 1) they promptly exit with a "Netif: > error, terminating listen loop" and 2) tun0 disappears and must be > recreated every time. > > 1) I tracked down the lines of code in mirage-net-unix that cause this > error message: > > let page = Io_page.get 1 in read t page >>= function | `Error _ -> printf > "Netif: error, terminating listen loop\n%!"; return () > > So it is running into an error when reading a page from the network. > It would be nice to pretty print the _ of `Error _ instead of drop it on > the floor. > > 2) I couldn't find anywhere in the code that remotely appeared to be > messing with or deleting the tun0 interface. But I wonder if the error I'm > seeing is due to the tun0 disappearing? > > -Robert > --047d7bfcfd50106f630514f8e769 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
An update: I just cloned the mirage-net-unix repo and= ran the tests. This is what I got:

sudo ./test.native
plugging i= nto tap0 with mac c2:9d:56:19:d7:2c..
Netif: connect tap0
connectedNetif: error, terminating listen loop
.
Ran: 1 tests in: 0.00 secon= ds.
OK

And the tun0 interface disappeared as well.
=



On Thu, Apr 30, 2015 at 2:55 PM, Robert Ream <= robertream@gmail.com> wrote:
Ok, I'm st= ill stumped.

Two things happen with pretty much all of the net= work examples when I build and execute them for unix: 1) they promptly exit= with a "Netif: error, terminating listen loop" and 2) tun0 disap= pears and must be recreated every time.

1) I tracked down the lines of code in mirage-net-unix tha= t cause this error message:
let pag= e =3D Io_page.get 1 in read t= page >>= =3D function | `Error _<= span style=3D"color:rgb(51,51,51);line-height:18.2000007629395px"> -> = printf "Netif: error, terminating listen loop\n%!"; = return ()

=
So= it is running into an error when reading a page from the network.
It would be nice to pretty print the _ of `Error _ instead of dro= p it on the floor.

2) I couldn't find = anywhere in the code that remotely appeared to be messing with or deleting = the tun0 interface. But I wonder if the error I'm seeing is due to the = tun0 disappearing?
<= br>
-Robert

--047d7bfcfd50106f630514f8e769-- --===============1394627386574588112== 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 --===============1394627386574588112==--