emberian · October 15, 2018 04:17
diff --git a/lists.robigalia.org.txt b/lists.robigalia.org.txt
 From grahamnorthup at yahoo.com  Wed Dec 23 19:11:28 2015
 From: grahamnorthup at yahoo.com (Graham Northup)
 Date: Wed, 23 Dec 2015 19:11:28 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 In-Reply-To: <20151223081446.GA3955@roger>
 References: <20151223081446.GA3955@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 Great, now I can't stop playing bootchess. I hope you're happy.

 > As a status update, I'm currently working on a contribution guide
 > and commit signing policy. I've "stolen" Rust's CONTRIBUTORS.md and
 > am modifying it heavily to be suitable for our purposes. I'll send
 > out a draft for review (especially by Graham) when it's ready in
 > the next day or so.

 ..."especially by [me]?" You're making it sound like I'm critical or
 something :P

 > ...For example, did you know that you can cause an object to "leak"
 > by overwriting its master capability with seL4_CNode_Move? Do that
 > with an untyped memory capability, and you've just lost physical
 > memory permanently!  At least, that's my current understanding.

 It's still there, it's just hiding--or, rather, the kernel would get
 annoyed if you tried to get to it :P

 > ...Progress here is slow due to the holidays and family/friend
 > visitations, but I expect it to pick up a lot after the new year.

 I'm in a similar situation at the moment, but I am taking the stinkpad
 out for a drive, and I'd be glad to contribute once I can get a
 working build on this thing again--id est, once the ol' README or a
 functional equivalent resurfaces so I can set up the build environment
 again :P . I suppose, in the meantime, I should get a working Rust
 environment, which is 200% more FUN with Gentoo...

 In any case, have a good one; I'll be listening for the moment :)

 On 12/23/2015 03:14 AM, Corey Richardson wrote:
 > Hey all,
 > 
 > One neat thing to do would be setting up some web-based client-side
 > x86 VM on robigalia.org with a demo of robigalia. It could also
 > have other sel4-based applications. In the future, when the RISC-V
 > port is mainlined and there's Rust support for it, we could use
 > angel or jor1k as well.
 > 
 > I know it's possible to compile qemu with emscripten, which might
 > be hard (I'm not sure), but there's also http://copy.sh/v86/ which
 > may be easier to get started with if it has enough emulated
 > hardware for sel4 to initialize (I suspect it does).
 > 
 > This is an independent nice-to-have project, if anyone wants to do
 > it.
 > 
 > Tracking issue: https://gitlab.com/robigalia/meta/issues/2
 > 
 > -- cmr +16032392210 http://octayn.net/
 > 
 > 
 > 
 > _______________________________________________ Robigalia-dev
 > mailing list Robigalia-dev at lists.robigalia.org 
 > http://lists.robigalia.org/listinfo/robigalia-dev
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWezgtAAoJEF0ADm9Tk3b79qAP/1y3MAoQxp3nfERh1x9LMJtW
 Qho4rTQFSkBpsc5XDOmzZjjfeb5rgAD64BntN4TDjmvO58wH2kpj7iQLwsqG+mxD
 gQx0RqVlp6qbawK8UMB/ydVBh+s8T1rbeuPe/fk9lgpslRAfwqOvbpGr7rzpUdRc
 AzpdLYhazvoA6HUyNLC8BwivHLIghaIe3Sm750XqS67fjrLJ75c4bw9uChuKApx/
 YMFQTLZspd7HcVfyZl8y3vEhogylS2wS4j7xVmOHwyxnzha01NB/++7qMyyXUsAr
 fphYp3Lxz6tTIEr0Fe4Unwf5an8ITNIMhaWZC8+D5Z0Bv55XQUo+UWWkB9HRy1KY
 vJFvv//m7cS1xX8YdyrBQVmkkQwEHdVNZp4jIDtYECnhtl8DA4d7wZTSYhjTj6fL
 MvwzJ9pBQbXn02UwlI3Sx2+FxhQcGkwepQxmbI118zzc+ROrVNwMpwxV1fcxDf9t
 xCpIOIvYD7rKjg7+4LiRsAwc1va+aqfKHfptBQlZYdV68DtMtq6Uwni6Y+owcZLI
 T4pH+NPFmEjrMgu34wD71qNtktS9Sofu6grqQCOEGtfwx1AnpVo0wAb4X77BAlqq
 RTjO6ebQ3aT7R6py8t663uIRdBQuH6R9FrHTHZSnsj2j83w2ueg8uKIHPi0EWXLC
 QQU5MXbV0HmsCeyDR2CC
 =DS00
 -----END PGP SIGNATURE-----
 _______________________________________________
 Robigalia-dev mailing list
 Robigalia-dev at lists.robigalia.org
 http://lists.robigalia.org/listinfo/robigalia-dev

 From corey at octayn.net  Wed Dec 23 03:14:47 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 03:14:47 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 Message-ID: <20151223081446.GA3955@roger>

 Hey all,

 One neat thing to do would be setting up some web-based client-side x86 VM on
 robigalia.org with a demo of robigalia. It could also have other sel4-based
 applications. In the future, when the RISC-V port is mainlined and there's
 Rust support for it, we could use angel or jor1k as well.

 I know it's possible to compile qemu with emscripten, which might be hard (I'm
 not sure), but there's also http://copy.sh/v86/ which may be easier to get
 started with if it has enough emulated hardware for sel4 to initialize (I
 suspect it does).

 This is an independent nice-to-have project, if anyone wants to do it.

 Tracking issue: https://gitlab.com/robigalia/meta/issues/2

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/2c664647/attachment.asc>
 -------------- next part --------------
 _______________________________________________
 Robigalia-dev mailing list
 Robigalia-dev at lists.robigalia.org
 http://lists.robigalia.org/listinfo/robigalia-dev

 From corey at octayn.net  Wed Dec 23 02:54:44 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 02:54:44 -0500
 Subject: [Robigalia-dev] Migrating to GNU mailman, status update
 Message-ID: <20151223075444.GB3239@roger>

 In the interest of avoiding Google Groups for these reasons:

 1. It's proprietary software
 2. It likes to mangle emails in non-MIME compliant ways

 As a consequence of 2:

 1. It mangles PGP/MIME messages
 2. It mangles patches sent with git-send-email
 3. It causes duplicated messages in threads for senders (one being the message
   sent to the mail gateway, the other being the mangled message sent back from
   the list)

 I have setup a GNU mailman instance at https://lists.robigalia.org. All
 current subscribers to robigalia-dev have been subscribed to the corresponding
 list there. After this mail is delivered I'll be putting the Google Group into
 read-only mode. I'm currently working on migrating the Google Group archive
 into the mailman archive. I've already got the archive scraped, I just need to
 massage it into a form that mailman feels happy with (I expect a little bit of
 sed and an elaborate shell pipeline in my future).

 As a status update, I'm currently working on a contribution guide and commit
 signing policy. I've "stolen" Rust's CONTRIBUTORS.md and am modifying it
 heavily to be suitable for our purposes. I'll send out a draft for review
 (especially by Graham) when it's ready in the next day or so.

 I'm also designing the high-level interface to seL4 kernel objects, and in the
 process mastering all the quirks of the API by studying the abstract
 specification.  For example, did you know that you can cause an object to
 "leak" by overwriting its master capability with seL4_CNode_Move? Do that with
 an untyped memory capability, and you've just lost physical memory
 permanently!  At least, that's my current understanding ;). Progress here is
 slow due to the holidays and family/friend visitations, but I expect it to
 pick up a lot after the new year.

 And, a personal aside, my Australian visa was approved yesterday, quite a bit
 earlier than I was expecting. Accordingly, my Robigalia timeslice has shrunk
 in deference of trip planning and doubling down on learning Isabelle.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/37862b12/attachment.asc>
 -------------- next part --------------
 _______________________________________________
 Robigalia-dev mailing list
 Robigalia-dev at lists.robigalia.org
 http://lists.robigalia.org/listinfo/robigalia-dev

 From corey at octayn.net  Fri Dec 18 04:09:47 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 18 Dec 2015 04:09:47 -0500
 Subject: x86 hello world application
 Message-ID: <20151218090947.GA23205@roger>

 Hello all,

 Binaries run! I've created two new repositories. The first is sel4-start. This
 contains the entry point glue for the initial thread. The second is
 hello-world. This is a simple crate using sel4-start that prints hello-world
 and then returns. sel4-start doesn't like it when main returns, so it just
 aborts at the moment by executing ud2. There's no real way to fix this in the
 long run. The initial thread should really never return -- it should either be
 long lived, or clean itself up by deleting its TCB.

 There's also been some changes to the vagrant vm and rust-sel4. Plus the
 ubuntu base image was updated upstream. It's best to just "vagrant destroy"
 and "vagrant up" again, after pulling all the things.

 Next up on the roadmap is the higher-level seL4 interface and memory
 allocation.

 If anyone has a copy of the original README from the devbox, please send it to
 me. Somehow it's gotten lost to the sands of time.

 Links:

 https://gitlab.com/robigalia/sel4-start

 https://gitlab.com/robigalia/hello-world

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151218/e46b1831/attachment.asc>

 From robigalia-dev at googlegroups.com  Fri Dec 18 12:20:45 2015
 From: robigalia-dev at googlegroups.com ('Graham Northup' via robigalia-dev)
 Date: Fri, 18 Dec 2015 12:20:45 -0500
 Subject: x86 hello world application
 In-Reply-To: <20151218090947.GA23205@roger>
 References: <20151218090947.GA23205@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 So what you're saying is that there's no clean way to power off a
 running seL4 system, then :P

 Also, your signature failed, as I suspect mine will too--Google groups
 seems to like to append some boilerplate at the bottom of this text.

 I'll take a look at that when I get a chance!

 Thanks,
 Graham

 On 12/18/2015 04:09 AM, Corey Richardson wrote:
 > Hello all,
 > 
 > Binaries run! I've created two new repositories. The first is
 > sel4-start. This contains the entry point glue for the initial
 > thread. The second is hello-world. This is a simple crate using
 > sel4-start that prints hello-world and then returns. sel4-start
 > doesn't like it when main returns, so it just aborts at the moment
 > by executing ud2. There's no real way to fix this in the long run.
 > The initial thread should really never return -- it should either
 > be long lived, or clean itself up by deleting its TCB.
 > 
 > There's also been some changes to the vagrant vm and rust-sel4.
 > Plus the ubuntu base image was updated upstream. It's best to just
 > "vagrant destroy" and "vagrant up" again, after pulling all the
 > things.
 > 
 > Next up on the roadmap is the higher-level seL4 interface and
 > memory allocation.
 > 
 > If anyone has a copy of the original README from the devbox, please
 > send it to me. Somehow it's gotten lost to the sands of time.
 > 
 > Links:
 > 
 > https://gitlab.com/robigalia/sel4-start
 > 
 > https://gitlab.com/robigalia/hello-world
 > 
 > -- cmr +16032392210 http://octayn.net/
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWdEBqAAoJEF0ADm9Tk3b7k68P/3yot0jWxXYG8pvAHjEFb49z
 2+47CJkkHUjSt5NhzevOpKde1xFHULUts2uaY5vV6BVSkB8eMcOEp679yYx6AaEE
 dYyBOBEwZUqfJ0JofHf4sLbkB3GMKaFP6u2nuv/v/1Pen0sTPcruDish1eKTeZfU
 uKwSRidT2m1vf3slEQtmyPmRXlzIIoXq8q+meZX8HybDeYU+hXyv+tyZPE2NMPiy
 3YgDfeRjn1le/UMavC9fNrVhQ0uo8HxUzQJrVY+/7r3vStgzeaXzplH+PP39MKGs
 WTW4vIjrldOeXO7Kd8y+4nGOOokfne3EgftfP7V4j4UCjsOiwq7GhJAcMkUy3/BL
 7kKDKFvdoFgTNPhuMXv+v/A/cNNvBe4/TeulT3naqdbeclM/k0RxdoIzbXKz4YXL
 LHiSBvzKSXUFMG8oPTQiHW2oFtvs0rlIZhgLZpxt6i2XHA/4OZb9ITTu7eX2jDYQ
 9sQrUdgDFvrKkadPNDTVL98CKv6+x7S6a7lXbygb9ykS0oShUqDLxA+ZjI/2N/ek
 aKebODdqpwnTMG1bgpy1Ye+Y88EkbkUCXhWUU45K4/5DzzmshnaXN5KgvC4Iw4c/
 tCvwzKAkt/s2bVXnxKpVo2r3ip6Dinh9Xb3DwMNwQW5iE4dSluctHvhvahppjqhn
 DgKIzceeAIJv6C6t0mx1
 =pQb7
 -----END PGP SIGNATURE-----

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/5674406D.907%40yahoo.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Fri Dec 18 23:14:21 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 18 Dec 2015 23:14:21 -0500
 Subject: x86 hello world application
 In-Reply-To: <[email protected]>
 References: <20151218090947.GA23205@roger>
 <[email protected]>
 Message-ID: <20151219041421.GA3000@roger>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA512

 On Fri, Dec 18, 2015 at 12:20:45PM -0500, 'Graham Northup' via robigalia-dev wrote:
 > So what you're saying is that there's no clean way to power off a
 > running seL4 system, then :P
 >

 That is the case! There is a debug halt syscall, but it's just a hlt jmp -1
 loop. There might be ACPI or other power management drivers somewhere, but I
 haven't seen them. There's a tiny bit of stuff in libplatsupport. I imagine
 ACPICA could be made to run with relative ease, were there interest in that.

 But honestly, who needs to power off a running system? ;)

 > Also, your signature failed, as I suspect mine will too--Google groups
 > seems to like to append some boilerplate at the bottom of this text.
 >

 That's a shame. Google Groups modifies the message part of the
 multipart/signed message, which is a no-no. GNU Mailman gets this right, at
 least, by appending a new text/plain part instead of modifying the original.
 I'll start using inline signatures here - that ought to be fine (and yours
 was) because the boilerplate is appended to the rest of the message body.

 - --
 cmr
 +16032392210
 http://octayn.net/
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQEcBAEBCgAGBQJWdNl/AAoJEJkCeK12JDMUKrMH/Ry83NXUJpXv6Ai5wEnM7hnh
 39NjYLhtnPwfrZiIzCH7lUFNWChkNMGH/ScsoyZTLf+It0PaXhyzvHXN6k7VG0Z5
 r2L1YcZzJVqIm1S4uTk/L6qjVXGQ9RTP2vsnQO65hZPhz3si7Mmc7cBrJmKNpEZq
 Z82JWKaqarjRPVJdckj/rTXWCdsrttcNbLHeMDVTHuTN1ShYpl3fQB2qUcaNuRgo
 5KUK362jECzIXAXiZJvLeF2850vcna5ZhXin3vV0Tq3zhoNmHtcuqlK/a7scysxN
 BhEpOBklFBPCrZ+ww7cMArGxdthaJ/FRi9b20XGo1TV1IWEhbt3f7QLfUGtP1Jg=
 =AWJz
 -----END PGP SIGNATURE-----



 From corey at octayn.net  Sun Dec 20 20:05:49 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sun, 20 Dec 2015 20:05:49 -0500
 Subject: rust-sel4 repo renamed to sel4-sys
 Message-ID: <20151221010549.GA18380@roger>

 Hey all,

 I've renamed the rust-sel4 repo to sel4-sys. You'll need to update your git
 remotes:

    cd devbox
    git pull # to get the updates to .subrepos
    mv rust-sel4 sel4-sys
    cd sel4-sys
    git remote set-url upstream ssh://git at gitlab.com/robigalia/sel4-sys.git

 I'll try not to do that again in the future.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151220/78f4f0ad/attachment.asc>

 From corey at octayn.net  Fri Dec  4 22:05:50 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 4 Dec 2015 22:05:50 -0500
 Subject: HTTPS on robigalia.org
 Message-ID: <20151205030550.GA10596@roger>

 Hey all,

 I've deployed HTTPS on https://robigalia.org and https://doc.robigalia.org, using
 http://letsencrypt.org/. All requests over plaintext HTTP will now redirect
 to HTTPS. Eventually (in probably a year or so), plaintext HTTP will be
 disabled.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151204/072a9213/attachment.asc>

 From corey at octayn.net  Wed Dec 23 02:54:44 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 02:54:44 -0500
 Subject: [Robigalia-dev] Migrating to GNU mailman, status update
 Message-ID: <20151223075444.GB3239@roger>

 In the interest of avoiding Google Groups for these reasons:

 1. It's proprietary software
 2. It likes to mangle emails in non-MIME compliant ways

 As a consequence of 2:

 1. It mangles PGP/MIME messages
 2. It mangles patches sent with git-send-email
 3. It causes duplicated messages in threads for senders (one being the message
   sent to the mail gateway, the other being the mangled message sent back from
   the list)

 I have setup a GNU mailman instance at https://lists.robigalia.org. All
 current subscribers to robigalia-dev have been subscribed to the corresponding
 list there. After this mail is delivered I'll be putting the Google Group into
 read-only mode. I'm currently working on migrating the Google Group archive
 into the mailman archive. I've already got the archive scraped, I just need to
 massage it into a form that mailman feels happy with (I expect a little bit of
 sed and an elaborate shell pipeline in my future).

 As a status update, I'm currently working on a contribution guide and commit
 signing policy. I've "stolen" Rust's CONTRIBUTORS.md and am modifying it
 heavily to be suitable for our purposes. I'll send out a draft for review
 (especially by Graham) when it's ready in the next day or so.

 I'm also designing the high-level interface to seL4 kernel objects, and in the
 process mastering all the quirks of the API by studying the abstract
 specification.  For example, did you know that you can cause an object to
 "leak" by overwriting its master capability with seL4_CNode_Move? Do that with
 an untyped memory capability, and you've just lost physical memory
 permanently!  At least, that's my current understanding ;). Progress here is
 slow due to the holidays and family/friend visitations, but I expect it to
 pick up a lot after the new year.

 And, a personal aside, my Australian visa was approved yesterday, quite a bit
 earlier than I was expecting. Accordingly, my Robigalia timeslice has shrunk
 in deference of trip planning and doubling down on learning Isabelle.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/37862b12/attachment-0001.asc>

 From corey at octayn.net  Wed Dec 23 03:14:47 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 03:14:47 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 Message-ID: <20151223081446.GA3955@roger>

 Hey all,

 One neat thing to do would be setting up some web-based client-side x86 VM on
 robigalia.org with a demo of robigalia. It could also have other sel4-based
 applications. In the future, when the RISC-V port is mainlined and there's
 Rust support for it, we could use angel or jor1k as well.

 I know it's possible to compile qemu with emscripten, which might be hard (I'm
 not sure), but there's also http://copy.sh/v86/ which may be easier to get
 started with if it has enough emulated hardware for sel4 to initialize (I
 suspect it does).

 This is an independent nice-to-have project, if anyone wants to do it.

 Tracking issue: https://gitlab.com/robigalia/meta/issues/2

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/2c664647/attachment-0001.asc>

 From grahamnorthup at yahoo.com  Wed Dec 23 19:11:28 2015
 From: grahamnorthup at yahoo.com (Graham Northup)
 Date: Wed, 23 Dec 2015 19:11:28 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 In-Reply-To: <20151223081446.GA3955@roger>
 References: <20151223081446.GA3955@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 Great, now I can't stop playing bootchess. I hope you're happy.

 > As a status update, I'm currently working on a contribution guide
 > and commit signing policy. I've "stolen" Rust's CONTRIBUTORS.md and
 > am modifying it heavily to be suitable for our purposes. I'll send
 > out a draft for review (especially by Graham) when it's ready in
 > the next day or so.

 ..."especially by [me]?" You're making it sound like I'm critical or
 something :P

 > ...For example, did you know that you can cause an object to "leak"
 > by overwriting its master capability with seL4_CNode_Move? Do that
 > with an untyped memory capability, and you've just lost physical
 > memory permanently!  At least, that's my current understanding.

 It's still there, it's just hiding--or, rather, the kernel would get
 annoyed if you tried to get to it :P

 > ...Progress here is slow due to the holidays and family/friend
 > visitations, but I expect it to pick up a lot after the new year.

 I'm in a similar situation at the moment, but I am taking the stinkpad
 out for a drive, and I'd be glad to contribute once I can get a
 working build on this thing again--id est, once the ol' README or a
 functional equivalent resurfaces so I can set up the build environment
 again :P . I suppose, in the meantime, I should get a working Rust
 environment, which is 200% more FUN with Gentoo...

 In any case, have a good one; I'll be listening for the moment :)

 On 12/23/2015 03:14 AM, Corey Richardson wrote:
 > Hey all,
 > 
 > One neat thing to do would be setting up some web-based client-side
 > x86 VM on robigalia.org with a demo of robigalia. It could also
 > have other sel4-based applications. In the future, when the RISC-V
 > port is mainlined and there's Rust support for it, we could use
 > angel or jor1k as well.
 > 
 > I know it's possible to compile qemu with emscripten, which might
 > be hard (I'm not sure), but there's also http://copy.sh/v86/ which
 > may be easier to get started with if it has enough emulated
 > hardware for sel4 to initialize (I suspect it does).
 > 
 > This is an independent nice-to-have project, if anyone wants to do
 > it.
 > 
 > Tracking issue: https://gitlab.com/robigalia/meta/issues/2
 > 
 > -- cmr +16032392210 http://octayn.net/
 > 
 > 
 > 
 > _______________________________________________ Robigalia-dev
 > mailing list Robigalia-dev at lists.robigalia.org 
 > http://lists.robigalia.org/listinfo/robigalia-dev
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWezgtAAoJEF0ADm9Tk3b79qAP/1y3MAoQxp3nfERh1x9LMJtW
 Qho4rTQFSkBpsc5XDOmzZjjfeb5rgAD64BntN4TDjmvO58wH2kpj7iQLwsqG+mxD
 gQx0RqVlp6qbawK8UMB/ydVBh+s8T1rbeuPe/fk9lgpslRAfwqOvbpGr7rzpUdRc
 AzpdLYhazvoA6HUyNLC8BwivHLIghaIe3Sm750XqS67fjrLJ75c4bw9uChuKApx/
 YMFQTLZspd7HcVfyZl8y3vEhogylS2wS4j7xVmOHwyxnzha01NB/++7qMyyXUsAr
 fphYp3Lxz6tTIEr0Fe4Unwf5an8ITNIMhaWZC8+D5Z0Bv55XQUo+UWWkB9HRy1KY
 vJFvv//m7cS1xX8YdyrBQVmkkQwEHdVNZp4jIDtYECnhtl8DA4d7wZTSYhjTj6fL
 MvwzJ9pBQbXn02UwlI3Sx2+FxhQcGkwepQxmbI118zzc+ROrVNwMpwxV1fcxDf9t
 xCpIOIvYD7rKjg7+4LiRsAwc1va+aqfKHfptBQlZYdV68DtMtq6Uwni6Y+owcZLI
 T4pH+NPFmEjrMgu34wD71qNtktS9Sofu6grqQCOEGtfwx1AnpVo0wAb4X77BAlqq
 RTjO6ebQ3aT7R6py8t663uIRdBQuH6R9FrHTHZSnsj2j83w2ueg8uKIHPi0EWXLC
 QQU5MXbV0HmsCeyDR2CC
 =DS00
 -----END PGP SIGNATURE-----


 From corey at octayn.net  Sat Dec 26 05:07:11 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 26 Dec 2015 05:07:11 -0500
 Subject: [robigalia-dev] Archives reconstructed
 Message-ID: <20151226100711.GA12626@roger>

 Hi all,

 The archives have been migrated from google groups:

 https://lists.robigalia.org/pipermail/robigalia-dev/

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151226/8e0fb916/attachment.asc>

 From corey at octayn.net  Sat Dec 26 05:09:44 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 26 Dec 2015 05:09:44 -0500
 Subject: [robigalia-dev] Contributing documentation + code of conduct
 Message-ID: <20151226100944.GB12626@roger>

 Hi all,

 I've pushed the code of conduct (adapted from
 https://github.com/todogroup/opencodeofconduct) and contributing
 documentation. It's up at https://gitlab.com/robigalia/meta.

 Feedback requested.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151226/1e7eb15e/attachment.asc>

 From corey at octayn.net  Mon Dec 28 01:10:32 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 28 Dec 2015 01:10:32 -0500
 Subject: [robigalia-dev] PCI crate
 Message-ID: <20151228061032.GB8226@roger>

 Hi all,

 Quick update on current progress. I just uploaded the first draft of a crate
 for PCI (the bus, not the industry) access. Right now it just does basic
 brute-force enumeration. Once I write some tests and also test it in a VM,
 I'll add more sophisticated things like a complete getter/setter to the
 standard headers and capability traversal.

 This is towards a virtio driver - which is also in-progress. There's a repo,
 but I haven't pushed any code yet, since it depends on pci. For now I'm
 implementing as little as possible to get a NIC going in seL4 with Rust. Who
 wants to write the TCP/IP stack? ;)

 PCI crate: https://gitlab.com/robigalia/pci
 virtio crate: https://gitlab.com/robigalia/virtio

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151228/e726426e/attachment.asc>

 From corey at octayn.net  Tue Dec 29 04:25:17 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 29 Dec 2015 04:25:17 -0500
 Subject: [robigalia-dev] Today's progress
 Message-ID: <20151229092517.GB12185@roger>

 Lots of debugging and small fixes today. A summary:

 - Fixed issue with sel4-start that caused infinite loop of calling main

  Did a jmp instead of a call. Oops.

 - Add a dependency on rlibc to sel4-sys

  This defines some important functions: memset, memcpy, memcmp, memmove.

 - Tweak the i686-sel4-unknown target spec

  Re-enable use of compiler-rt, force relocation model to "static" (the loader
  doesn't know how to deal with PIC, not sure I want it to!) Also use LLVM
  triple of i686-elf instead of i686-unknown-linux-gnu. I don't know what
  ramifications this has practically, but it doesn't hurt.

 - Derive some common traits for structs in sel4-sys

  Most structs got a healthy dose of Copy, Clone, Debug, PartialEq, and Eq.

 - devbox bootstrap saw some assorted fixes, most importantly building
  compiler-rt for 32-bit x86.

  You'll need to re-provision your Vagrant VMs.

 I've also got the "high-level" interface to seL4 almost hammered out. I
 thought I'd have the PCI bus scanning done today, but it turns out debugging
 that stuff is hard (who would have guessed), especially when you don't have
 any way to inspect hardware errors yet!

 Tomorrow I'll finish the high-level interface and start looking at using
 GitLab's continuous integration service to automate uploading docs to
 doc.robigalia.org, as well as possibly doing testing. Some of this code is
 really hard to do automated tests with, but that's not an excuse for not
 trying. I'll also re-write the devbox README, since it appears that it really
 has disappeared into the aether.

 Until then,
 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151229/2d5de568/attachment.asc>

 From grahamnorthup at yahoo.com  Wed Dec 23 19:11:28 2015
 From: grahamnorthup at yahoo.com (Graham Northup)
 Date: Wed, 23 Dec 2015 19:11:28 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 In-Reply-To: <20151223081446.GA3955@roger>
 References: <20151223081446.GA3955@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 Great, now I can't stop playing bootchess. I hope you're happy.

 > As a status update, I'm currently working on a contribution guide
 > and commit signing policy. I've "stolen" Rust's CONTRIBUTORS.md and
 > am modifying it heavily to be suitable for our purposes. I'll send
 > out a draft for review (especially by Graham) when it's ready in
 > the next day or so.

 ..."especially by [me]?" You're making it sound like I'm critical or
 something :P

 > ...For example, did you know that you can cause an object to "leak"
 > by overwriting its master capability with seL4_CNode_Move? Do that
 > with an untyped memory capability, and you've just lost physical
 > memory permanently!  At least, that's my current understanding.

 It's still there, it's just hiding--or, rather, the kernel would get
 annoyed if you tried to get to it :P

 > ...Progress here is slow due to the holidays and family/friend
 > visitations, but I expect it to pick up a lot after the new year.

 I'm in a similar situation at the moment, but I am taking the stinkpad
 out for a drive, and I'd be glad to contribute once I can get a
 working build on this thing again--id est, once the ol' README or a
 functional equivalent resurfaces so I can set up the build environment
 again :P . I suppose, in the meantime, I should get a working Rust
 environment, which is 200% more FUN with Gentoo...

 In any case, have a good one; I'll be listening for the moment :)

 On 12/23/2015 03:14 AM, Corey Richardson wrote:
 > Hey all,
 > 
 > One neat thing to do would be setting up some web-based client-side
 > x86 VM on robigalia.org with a demo of robigalia. It could also
 > have other sel4-based applications. In the future, when the RISC-V
 > port is mainlined and there's Rust support for it, we could use
 > angel or jor1k as well.
 > 
 > I know it's possible to compile qemu with emscripten, which might
 > be hard (I'm not sure), but there's also http://copy.sh/v86/ which
 > may be easier to get started with if it has enough emulated
 > hardware for sel4 to initialize (I suspect it does).
 > 
 > This is an independent nice-to-have project, if anyone wants to do
 > it.
 > 
 > Tracking issue: https://gitlab.com/robigalia/meta/issues/2
 > 
 > -- cmr +16032392210 http://octayn.net/
 > 
 > 
 > 
 > _______________________________________________ Robigalia-dev
 > mailing list Robigalia-dev at lists.robigalia.org 
 > http://lists.robigalia.org/listinfo/robigalia-dev
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWezgtAAoJEF0ADm9Tk3b79qAP/1y3MAoQxp3nfERh1x9LMJtW
 Qho4rTQFSkBpsc5XDOmzZjjfeb5rgAD64BntN4TDjmvO58wH2kpj7iQLwsqG+mxD
 gQx0RqVlp6qbawK8UMB/ydVBh+s8T1rbeuPe/fk9lgpslRAfwqOvbpGr7rzpUdRc
 AzpdLYhazvoA6HUyNLC8BwivHLIghaIe3Sm750XqS67fjrLJ75c4bw9uChuKApx/
 YMFQTLZspd7HcVfyZl8y3vEhogylS2wS4j7xVmOHwyxnzha01NB/++7qMyyXUsAr
 fphYp3Lxz6tTIEr0Fe4Unwf5an8ITNIMhaWZC8+D5Z0Bv55XQUo+UWWkB9HRy1KY
 vJFvv//m7cS1xX8YdyrBQVmkkQwEHdVNZp4jIDtYECnhtl8DA4d7wZTSYhjTj6fL
 MvwzJ9pBQbXn02UwlI3Sx2+FxhQcGkwepQxmbI118zzc+ROrVNwMpwxV1fcxDf9t
 xCpIOIvYD7rKjg7+4LiRsAwc1va+aqfKHfptBQlZYdV68DtMtq6Uwni6Y+owcZLI
 T4pH+NPFmEjrMgu34wD71qNtktS9Sofu6grqQCOEGtfwx1AnpVo0wAb4X77BAlqq
 RTjO6ebQ3aT7R6py8t663uIRdBQuH6R9FrHTHZSnsj2j83w2ueg8uKIHPi0EWXLC
 QQU5MXbV0HmsCeyDR2CC
 =DS00
 -----END PGP SIGNATURE-----
 _______________________________________________
 Robigalia-dev mailing list
 Robigalia-dev at lists.robigalia.org
 http://lists.robigalia.org/listinfo/robigalia-dev

 From corey at octayn.net  Wed Dec 23 03:14:47 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 03:14:47 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 Message-ID: <20151223081446.GA3955@roger>

 Hey all,

 One neat thing to do would be setting up some web-based client-side x86 VM on
 robigalia.org with a demo of robigalia. It could also have other sel4-based
 applications. In the future, when the RISC-V port is mainlined and there's
 Rust support for it, we could use angel or jor1k as well.

 I know it's possible to compile qemu with emscripten, which might be hard (I'm
 not sure), but there's also http://copy.sh/v86/ which may be easier to get
 started with if it has enough emulated hardware for sel4 to initialize (I
 suspect it does).

 This is an independent nice-to-have project, if anyone wants to do it.

 Tracking issue: https://gitlab.com/robigalia/meta/issues/2

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/2c664647/attachment.asc>
 -------------- next part --------------
 _______________________________________________
 Robigalia-dev mailing list
 Robigalia-dev at lists.robigalia.org
 http://lists.robigalia.org/listinfo/robigalia-dev

 From corey at octayn.net  Wed Dec 23 02:54:44 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 02:54:44 -0500
 Subject: [Robigalia-dev] Migrating to GNU mailman, status update
 Message-ID: <20151223075444.GB3239@roger>

 In the interest of avoiding Google Groups for these reasons:

 1. It's proprietary software
 2. It likes to mangle emails in non-MIME compliant ways

 As a consequence of 2:

 1. It mangles PGP/MIME messages
 2. It mangles patches sent with git-send-email
 3. It causes duplicated messages in threads for senders (one being the message
   sent to the mail gateway, the other being the mangled message sent back from
   the list)

 I have setup a GNU mailman instance at https://lists.robigalia.org. All
 current subscribers to robigalia-dev have been subscribed to the corresponding
 list there. After this mail is delivered I'll be putting the Google Group into
 read-only mode. I'm currently working on migrating the Google Group archive
 into the mailman archive. I've already got the archive scraped, I just need to
 massage it into a form that mailman feels happy with (I expect a little bit of
 sed and an elaborate shell pipeline in my future).

 As a status update, I'm currently working on a contribution guide and commit
 signing policy. I've "stolen" Rust's CONTRIBUTORS.md and am modifying it
 heavily to be suitable for our purposes. I'll send out a draft for review
 (especially by Graham) when it's ready in the next day or so.

 I'm also designing the high-level interface to seL4 kernel objects, and in the
 process mastering all the quirks of the API by studying the abstract
 specification.  For example, did you know that you can cause an object to
 "leak" by overwriting its master capability with seL4_CNode_Move? Do that with
 an untyped memory capability, and you've just lost physical memory
 permanently!  At least, that's my current understanding ;). Progress here is
 slow due to the holidays and family/friend visitations, but I expect it to
 pick up a lot after the new year.

 And, a personal aside, my Australian visa was approved yesterday, quite a bit
 earlier than I was expecting. Accordingly, my Robigalia timeslice has shrunk
 in deference of trip planning and doubling down on learning Isabelle.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/37862b12/attachment.asc>
 -------------- next part --------------
 _______________________________________________
 Robigalia-dev mailing list
 Robigalia-dev at lists.robigalia.org
 http://lists.robigalia.org/listinfo/robigalia-dev

 From corey at octayn.net  Fri Dec 18 04:09:47 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 18 Dec 2015 04:09:47 -0500
 Subject: x86 hello world application
 Message-ID: <20151218090947.GA23205@roger>

 Hello all,

 Binaries run! I've created two new repositories. The first is sel4-start. This
 contains the entry point glue for the initial thread. The second is
 hello-world. This is a simple crate using sel4-start that prints hello-world
 and then returns. sel4-start doesn't like it when main returns, so it just
 aborts at the moment by executing ud2. There's no real way to fix this in the
 long run. The initial thread should really never return -- it should either be
 long lived, or clean itself up by deleting its TCB.

 There's also been some changes to the vagrant vm and rust-sel4. Plus the
 ubuntu base image was updated upstream. It's best to just "vagrant destroy"
 and "vagrant up" again, after pulling all the things.

 Next up on the roadmap is the higher-level seL4 interface and memory
 allocation.

 If anyone has a copy of the original README from the devbox, please send it to
 me. Somehow it's gotten lost to the sands of time.

 Links:

 https://gitlab.com/robigalia/sel4-start

 https://gitlab.com/robigalia/hello-world

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151218/e46b1831/attachment.asc>

 From robigalia-dev at googlegroups.com  Fri Dec 18 12:20:45 2015
 From: robigalia-dev at googlegroups.com ('Graham Northup' via robigalia-dev)
 Date: Fri, 18 Dec 2015 12:20:45 -0500
 Subject: x86 hello world application
 In-Reply-To: <20151218090947.GA23205@roger>
 References: <20151218090947.GA23205@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 So what you're saying is that there's no clean way to power off a
 running seL4 system, then :P

 Also, your signature failed, as I suspect mine will too--Google groups
 seems to like to append some boilerplate at the bottom of this text.

 I'll take a look at that when I get a chance!

 Thanks,
 Graham

 On 12/18/2015 04:09 AM, Corey Richardson wrote:
 > Hello all,
 > 
 > Binaries run! I've created two new repositories. The first is
 > sel4-start. This contains the entry point glue for the initial
 > thread. The second is hello-world. This is a simple crate using
 > sel4-start that prints hello-world and then returns. sel4-start
 > doesn't like it when main returns, so it just aborts at the moment
 > by executing ud2. There's no real way to fix this in the long run.
 > The initial thread should really never return -- it should either
 > be long lived, or clean itself up by deleting its TCB.
 > 
 > There's also been some changes to the vagrant vm and rust-sel4.
 > Plus the ubuntu base image was updated upstream. It's best to just
 > "vagrant destroy" and "vagrant up" again, after pulling all the
 > things.
 > 
 > Next up on the roadmap is the higher-level seL4 interface and
 > memory allocation.
 > 
 > If anyone has a copy of the original README from the devbox, please
 > send it to me. Somehow it's gotten lost to the sands of time.
 > 
 > Links:
 > 
 > https://gitlab.com/robigalia/sel4-start
 > 
 > https://gitlab.com/robigalia/hello-world
 > 
 > -- cmr +16032392210 http://octayn.net/
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWdEBqAAoJEF0ADm9Tk3b7k68P/3yot0jWxXYG8pvAHjEFb49z
 2+47CJkkHUjSt5NhzevOpKde1xFHULUts2uaY5vV6BVSkB8eMcOEp679yYx6AaEE
 dYyBOBEwZUqfJ0JofHf4sLbkB3GMKaFP6u2nuv/v/1Pen0sTPcruDish1eKTeZfU
 uKwSRidT2m1vf3slEQtmyPmRXlzIIoXq8q+meZX8HybDeYU+hXyv+tyZPE2NMPiy
 3YgDfeRjn1le/UMavC9fNrVhQ0uo8HxUzQJrVY+/7r3vStgzeaXzplH+PP39MKGs
 WTW4vIjrldOeXO7Kd8y+4nGOOokfne3EgftfP7V4j4UCjsOiwq7GhJAcMkUy3/BL
 7kKDKFvdoFgTNPhuMXv+v/A/cNNvBe4/TeulT3naqdbeclM/k0RxdoIzbXKz4YXL
 LHiSBvzKSXUFMG8oPTQiHW2oFtvs0rlIZhgLZpxt6i2XHA/4OZb9ITTu7eX2jDYQ
 9sQrUdgDFvrKkadPNDTVL98CKv6+x7S6a7lXbygb9ykS0oShUqDLxA+ZjI/2N/ek
 aKebODdqpwnTMG1bgpy1Ye+Y88EkbkUCXhWUU45K4/5DzzmshnaXN5KgvC4Iw4c/
 tCvwzKAkt/s2bVXnxKpVo2r3ip6Dinh9Xb3DwMNwQW5iE4dSluctHvhvahppjqhn
 DgKIzceeAIJv6C6t0mx1
 =pQb7
 -----END PGP SIGNATURE-----

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/5674406D.907%40yahoo.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Fri Dec 18 23:14:21 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 18 Dec 2015 23:14:21 -0500
 Subject: x86 hello world application
 In-Reply-To: <[email protected]>
 References: <20151218090947.GA23205@roger>
 <[email protected]>
 Message-ID: <20151219041421.GA3000@roger>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA512

 On Fri, Dec 18, 2015 at 12:20:45PM -0500, 'Graham Northup' via robigalia-dev wrote:
 > So what you're saying is that there's no clean way to power off a
 > running seL4 system, then :P
 >

 That is the case! There is a debug halt syscall, but it's just a hlt jmp -1
 loop. There might be ACPI or other power management drivers somewhere, but I
 haven't seen them. There's a tiny bit of stuff in libplatsupport. I imagine
 ACPICA could be made to run with relative ease, were there interest in that.

 But honestly, who needs to power off a running system? ;)

 > Also, your signature failed, as I suspect mine will too--Google groups
 > seems to like to append some boilerplate at the bottom of this text.
 >

 That's a shame. Google Groups modifies the message part of the
 multipart/signed message, which is a no-no. GNU Mailman gets this right, at
 least, by appending a new text/plain part instead of modifying the original.
 I'll start using inline signatures here - that ought to be fine (and yours
 was) because the boilerplate is appended to the rest of the message body.

 - --
 cmr
 +16032392210
 http://octayn.net/
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQEcBAEBCgAGBQJWdNl/AAoJEJkCeK12JDMUKrMH/Ry83NXUJpXv6Ai5wEnM7hnh
 39NjYLhtnPwfrZiIzCH7lUFNWChkNMGH/ScsoyZTLf+It0PaXhyzvHXN6k7VG0Z5
 r2L1YcZzJVqIm1S4uTk/L6qjVXGQ9RTP2vsnQO65hZPhz3si7Mmc7cBrJmKNpEZq
 Z82JWKaqarjRPVJdckj/rTXWCdsrttcNbLHeMDVTHuTN1ShYpl3fQB2qUcaNuRgo
 5KUK362jECzIXAXiZJvLeF2850vcna5ZhXin3vV0Tq3zhoNmHtcuqlK/a7scysxN
 BhEpOBklFBPCrZ+ww7cMArGxdthaJ/FRi9b20XGo1TV1IWEhbt3f7QLfUGtP1Jg=
 =AWJz
 -----END PGP SIGNATURE-----



 From corey at octayn.net  Sun Dec 20 20:05:49 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sun, 20 Dec 2015 20:05:49 -0500
 Subject: rust-sel4 repo renamed to sel4-sys
 Message-ID: <20151221010549.GA18380@roger>

 Hey all,

 I've renamed the rust-sel4 repo to sel4-sys. You'll need to update your git
 remotes:

    cd devbox
    git pull # to get the updates to .subrepos
    mv rust-sel4 sel4-sys
    cd sel4-sys
    git remote set-url upstream ssh://git at gitlab.com/robigalia/sel4-sys.git

 I'll try not to do that again in the future.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151220/78f4f0ad/attachment.asc>

 From corey at octayn.net  Fri Dec  4 22:05:50 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 4 Dec 2015 22:05:50 -0500
 Subject: HTTPS on robigalia.org
 Message-ID: <20151205030550.GA10596@roger>

 Hey all,

 I've deployed HTTPS on https://robigalia.org and https://doc.robigalia.org, using
 http://letsencrypt.org/. All requests over plaintext HTTP will now redirect
 to HTTPS. Eventually (in probably a year or so), plaintext HTTP will be
 disabled.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151204/072a9213/attachment.asc>

 From corey at octayn.net  Wed Dec 23 02:54:44 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 02:54:44 -0500
 Subject: [Robigalia-dev] Migrating to GNU mailman, status update
 Message-ID: <20151223075444.GB3239@roger>

 In the interest of avoiding Google Groups for these reasons:

 1. It's proprietary software
 2. It likes to mangle emails in non-MIME compliant ways

 As a consequence of 2:

 1. It mangles PGP/MIME messages
 2. It mangles patches sent with git-send-email
 3. It causes duplicated messages in threads for senders (one being the message
   sent to the mail gateway, the other being the mangled message sent back from
   the list)

 I have setup a GNU mailman instance at https://lists.robigalia.org. All
 current subscribers to robigalia-dev have been subscribed to the corresponding
 list there. After this mail is delivered I'll be putting the Google Group into
 read-only mode. I'm currently working on migrating the Google Group archive
 into the mailman archive. I've already got the archive scraped, I just need to
 massage it into a form that mailman feels happy with (I expect a little bit of
 sed and an elaborate shell pipeline in my future).

 As a status update, I'm currently working on a contribution guide and commit
 signing policy. I've "stolen" Rust's CONTRIBUTORS.md and am modifying it
 heavily to be suitable for our purposes. I'll send out a draft for review
 (especially by Graham) when it's ready in the next day or so.

 I'm also designing the high-level interface to seL4 kernel objects, and in the
 process mastering all the quirks of the API by studying the abstract
 specification.  For example, did you know that you can cause an object to
 "leak" by overwriting its master capability with seL4_CNode_Move? Do that with
 an untyped memory capability, and you've just lost physical memory
 permanently!  At least, that's my current understanding ;). Progress here is
 slow due to the holidays and family/friend visitations, but I expect it to
 pick up a lot after the new year.

 And, a personal aside, my Australian visa was approved yesterday, quite a bit
 earlier than I was expecting. Accordingly, my Robigalia timeslice has shrunk
 in deference of trip planning and doubling down on learning Isabelle.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/37862b12/attachment-0001.asc>

 From corey at octayn.net  Wed Dec 23 03:14:47 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 23 Dec 2015 03:14:47 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 Message-ID: <20151223081446.GA3955@roger>

 Hey all,

 One neat thing to do would be setting up some web-based client-side x86 VM on
 robigalia.org with a demo of robigalia. It could also have other sel4-based
 applications. In the future, when the RISC-V port is mainlined and there's
 Rust support for it, we could use angel or jor1k as well.

 I know it's possible to compile qemu with emscripten, which might be hard (I'm
 not sure), but there's also http://copy.sh/v86/ which may be easier to get
 started with if it has enough emulated hardware for sel4 to initialize (I
 suspect it does).

 This is an independent nice-to-have project, if anyone wants to do it.

 Tracking issue: https://gitlab.com/robigalia/meta/issues/2

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151223/2c664647/attachment-0001.asc>

 From grahamnorthup at yahoo.com  Wed Dec 23 19:11:28 2015
 From: grahamnorthup at yahoo.com (Graham Northup)
 Date: Wed, 23 Dec 2015 19:11:28 -0500
 Subject: [Robigalia-dev] Contribution idea: javascript VM demo
 In-Reply-To: <20151223081446.GA3955@roger>
 References: <20151223081446.GA3955@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 Great, now I can't stop playing bootchess. I hope you're happy.

 > As a status update, I'm currently working on a contribution guide
 > and commit signing policy. I've "stolen" Rust's CONTRIBUTORS.md and
 > am modifying it heavily to be suitable for our purposes. I'll send
 > out a draft for review (especially by Graham) when it's ready in
 > the next day or so.

 ..."especially by [me]?" You're making it sound like I'm critical or
 something :P

 > ...For example, did you know that you can cause an object to "leak"
 > by overwriting its master capability with seL4_CNode_Move? Do that
 > with an untyped memory capability, and you've just lost physical
 > memory permanently!  At least, that's my current understanding.

 It's still there, it's just hiding--or, rather, the kernel would get
 annoyed if you tried to get to it :P

 > ...Progress here is slow due to the holidays and family/friend
 > visitations, but I expect it to pick up a lot after the new year.

 I'm in a similar situation at the moment, but I am taking the stinkpad
 out for a drive, and I'd be glad to contribute once I can get a
 working build on this thing again--id est, once the ol' README or a
 functional equivalent resurfaces so I can set up the build environment
 again :P . I suppose, in the meantime, I should get a working Rust
 environment, which is 200% more FUN with Gentoo...

 In any case, have a good one; I'll be listening for the moment :)

 On 12/23/2015 03:14 AM, Corey Richardson wrote:
 > Hey all,
 > 
 > One neat thing to do would be setting up some web-based client-side
 > x86 VM on robigalia.org with a demo of robigalia. It could also
 > have other sel4-based applications. In the future, when the RISC-V
 > port is mainlined and there's Rust support for it, we could use
 > angel or jor1k as well.
 > 
 > I know it's possible to compile qemu with emscripten, which might
 > be hard (I'm not sure), but there's also http://copy.sh/v86/ which
 > may be easier to get started with if it has enough emulated
 > hardware for sel4 to initialize (I suspect it does).
 > 
 > This is an independent nice-to-have project, if anyone wants to do
 > it.
 > 
 > Tracking issue: https://gitlab.com/robigalia/meta/issues/2
 > 
 > -- cmr +16032392210 http://octayn.net/
 > 
 > 
 > 
 > _______________________________________________ Robigalia-dev
 > mailing list Robigalia-dev at lists.robigalia.org 
 > http://lists.robigalia.org/listinfo/robigalia-dev
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWezgtAAoJEF0ADm9Tk3b79qAP/1y3MAoQxp3nfERh1x9LMJtW
 Qho4rTQFSkBpsc5XDOmzZjjfeb5rgAD64BntN4TDjmvO58wH2kpj7iQLwsqG+mxD
 gQx0RqVlp6qbawK8UMB/ydVBh+s8T1rbeuPe/fk9lgpslRAfwqOvbpGr7rzpUdRc
 AzpdLYhazvoA6HUyNLC8BwivHLIghaIe3Sm750XqS67fjrLJ75c4bw9uChuKApx/
 YMFQTLZspd7HcVfyZl8y3vEhogylS2wS4j7xVmOHwyxnzha01NB/++7qMyyXUsAr
 fphYp3Lxz6tTIEr0Fe4Unwf5an8ITNIMhaWZC8+D5Z0Bv55XQUo+UWWkB9HRy1KY
 vJFvv//m7cS1xX8YdyrBQVmkkQwEHdVNZp4jIDtYECnhtl8DA4d7wZTSYhjTj6fL
 MvwzJ9pBQbXn02UwlI3Sx2+FxhQcGkwepQxmbI118zzc+ROrVNwMpwxV1fcxDf9t
 xCpIOIvYD7rKjg7+4LiRsAwc1va+aqfKHfptBQlZYdV68DtMtq6Uwni6Y+owcZLI
 T4pH+NPFmEjrMgu34wD71qNtktS9Sofu6grqQCOEGtfwx1AnpVo0wAb4X77BAlqq
 RTjO6ebQ3aT7R6py8t663uIRdBQuH6R9FrHTHZSnsj2j83w2ueg8uKIHPi0EWXLC
 QQU5MXbV0HmsCeyDR2CC
 =DS00
 -----END PGP SIGNATURE-----


 From corey at octayn.net  Sat Dec 26 05:07:11 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 26 Dec 2015 05:07:11 -0500
 Subject: [robigalia-dev] Archives reconstructed
 Message-ID: <20151226100711.GA12626@roger>

 Hi all,

 The archives have been migrated from google groups:

 https://lists.robigalia.org/pipermail/robigalia-dev/

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151226/8e0fb916/attachment.asc>

 From corey at octayn.net  Sat Dec 26 05:09:44 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 26 Dec 2015 05:09:44 -0500
 Subject: [robigalia-dev] Contributing documentation + code of conduct
 Message-ID: <20151226100944.GB12626@roger>

 Hi all,

 I've pushed the code of conduct (adapted from
 https://github.com/todogroup/opencodeofconduct) and contributing
 documentation. It's up at https://gitlab.com/robigalia/meta.

 Feedback requested.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151226/1e7eb15e/attachment.asc>

 From corey at octayn.net  Mon Dec 28 01:10:32 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 28 Dec 2015 01:10:32 -0500
 Subject: [robigalia-dev] PCI crate
 Message-ID: <20151228061032.GB8226@roger>

 Hi all,

 Quick update on current progress. I just uploaded the first draft of a crate
 for PCI (the bus, not the industry) access. Right now it just does basic
 brute-force enumeration. Once I write some tests and also test it in a VM,
 I'll add more sophisticated things like a complete getter/setter to the
 standard headers and capability traversal.

 This is towards a virtio driver - which is also in-progress. There's a repo,
 but I haven't pushed any code yet, since it depends on pci. For now I'm
 implementing as little as possible to get a NIC going in seL4 with Rust. Who
 wants to write the TCP/IP stack? ;)

 PCI crate: https://gitlab.com/robigalia/pci
 virtio crate: https://gitlab.com/robigalia/virtio

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151228/e726426e/attachment.asc>

 From corey at octayn.net  Tue Dec 29 04:25:17 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 29 Dec 2015 04:25:17 -0500
 Subject: [robigalia-dev] Today's progress
 Message-ID: <20151229092517.GB12185@roger>

 Lots of debugging and small fixes today. A summary:

 - Fixed issue with sel4-start that caused infinite loop of calling main

  Did a jmp instead of a call. Oops.

 - Add a dependency on rlibc to sel4-sys

  This defines some important functions: memset, memcpy, memcmp, memmove.

 - Tweak the i686-sel4-unknown target spec

  Re-enable use of compiler-rt, force relocation model to "static" (the loader
  doesn't know how to deal with PIC, not sure I want it to!) Also use LLVM
  triple of i686-elf instead of i686-unknown-linux-gnu. I don't know what
  ramifications this has practically, but it doesn't hurt.

 - Derive some common traits for structs in sel4-sys

  Most structs got a healthy dose of Copy, Clone, Debug, PartialEq, and Eq.

 - devbox bootstrap saw some assorted fixes, most importantly building
  compiler-rt for 32-bit x86.

  You'll need to re-provision your Vagrant VMs.

 I've also got the "high-level" interface to seL4 almost hammered out. I
 thought I'd have the PCI bus scanning done today, but it turns out debugging
 that stuff is hard (who would have guessed), especially when you don't have
 any way to inspect hardware errors yet!

 Tomorrow I'll finish the high-level interface and start looking at using
 GitLab's continuous integration service to automate uploading docs to
 doc.robigalia.org, as well as possibly doing testing. Some of this code is
 really hard to do automated tests with, but that's not an excuse for not
 trying. I'll also re-write the devbox README, since it appears that it really
 has disappeared into the aether.

 Until then,
 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20151229/2d5de568/attachment.asc>
 From corey at octayn.net  Wed Oct 28 02:12:16 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 28 Oct 2015 02:12:16 -0400
 Subject: Status update and near-term roadmap
 Message-ID: <1446012736.1614832.422237985.396684CC@webmail.messagingengine.com>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 # A quick update on the system design

 I've been focusing on memory management recently. In particular, the virtual
 memory subsystem that will lie underneath Robigo. One challenge is that
 ideally this subsystem would be usable for non-POSIX components on seL4 as
 well. I've been looking into the design constraints and existing solutions to
 the problems from the UNIX side of things. One very relevant documentation is
 Chuck Cranor's PhD dissertation, [1]. His uvm lies underneath most modern
 BSDs. The primary goals of our virtual memory subsystem will be efficient
 copy-on-write semantics for vfork and soforth and enabling zero-copy IPC and
 I/O based on page transfer rather than data copying. This shouldn't be
 incredibly challenging, but getting it right is important and there are lots
 of details.

 [1] - http://chuck.cranor.org/p/diss.pdf

 # Near-term roadmap

 In the interest of not letting the perfect be the enemy of the good, I'm going
 to get a prototype application working on x86 in a VM ASAP. Having something
 tangible to play with should be motivating. I'll be writing up some blog posts
 about how it all fits together, for others interested in using Rust with seL4
 for other purposes.

 # Going to NICTA

 Some of you know already, but I'll be travelling to Australia for 8 months
 in 2016 to work on seL4. I'll be on their verification team, but Rust and
 Robigalia won't be far from my mind. I expect this will consume most of my
 extra hacking-time for those months, so progress should be swift.

 # Abandoning ARM (for now)

 The ARM port of rust-sel4 has been stagnant because I don't have good means to
 test it. The board I have (Savage Board) isn't officially supported, and I've
 been having some mysterious issues with it, that I shouldn't be given that
 it's a pretty stock i.MX6 platform. If someone wants to play with it, let me
 know and I'll show you how you can flash the firmware and soforth. You can do
 it all from Linux. It also supports fastboot (via u-boot).


 That's all for now. I'll be around!

 /cmr
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQEcBAEBCAAGBQJWMGckAAoJEJkCeK12JDMUHGIH/0g9K7ksjuF/Sn1t16f+nods
 DiB59xRSCKYwGa+y6CUXTqLaRKkpS+RkXW5w4egBAa8r8m2c1+/D5qFJkjZIxnSh
 J7aBxK8xto5bno3dngn3KchtvUVD7P0jQi20GFrX9IobriGEzxERJs+uc9VBmlxW
 zTobtXDvIlFbUM/0Dl7xSaH748QikvqaR+WaADZPNAcZQ3ui/HpDqZCVSt771HnH
 WzMennnstmZPw8/GRP1AkOEPgh8VTXwzsqYFtxSOqddi4zQJeyEJW/nu0ReQCLIa
 LdbGewTOZutC9/nw73O1c+LeDTC5TUzUwnc11MwYxCYLjbiSkCGWZHVYUsgyBK4=
 =Ph57
 -----END PGP SIGNATURE-----



 From corey at octayn.net  Wed Oct 28 02:12:16 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 28 Oct 2015 02:12:16 -0400
 Subject: Status update and near-term roadmap
 Message-ID: <1446012736.1614832.422237985.396684CC@webmail.messagingengine.com>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 # A quick update on the system design

 I've been focusing on memory management recently. In particular, the virtual
 memory subsystem that will lie underneath Robigo. One challenge is that
 ideally this subsystem would be usable for non-POSIX components on seL4 as
 well. I've been looking into the design constraints and existing solutions to
 the problems from the UNIX side of things. One very relevant documentation is
 Chuck Cranor's PhD dissertation, [1]. His uvm lies underneath most modern
 BSDs. The primary goals of our virtual memory subsystem will be efficient
 copy-on-write semantics for vfork and soforth and enabling zero-copy IPC and
 I/O based on page transfer rather than data copying. This shouldn't be
 incredibly challenging, but getting it right is important and there are lots
 of details.

 [1] - http://chuck.cranor.org/p/diss.pdf

 # Near-term roadmap

 In the interest of not letting the perfect be the enemy of the good, I'm going
 to get a prototype application working on x86 in a VM ASAP. Having something
 tangible to play with should be motivating. I'll be writing up some blog posts
 about how it all fits together, for others interested in using Rust with seL4
 for other purposes.

 # Going to NICTA

 Some of you know already, but I'll be travelling to Australia for 8 months
 in 2016 to work on seL4. I'll be on their verification team, but Rust and
 Robigalia won't be far from my mind. I expect this will consume most of my
 extra hacking-time for those months, so progress should be swift.

 # Abandoning ARM (for now)

 The ARM port of rust-sel4 has been stagnant because I don't have good means to
 test it. The board I have (Savage Board) isn't officially supported, and I've
 been having some mysterious issues with it, that I shouldn't be given that
 it's a pretty stock i.MX6 platform. If someone wants to play with it, let me
 know and I'll show you how you can flash the firmware and soforth. You can do
 it all from Linux. It also supports fastboot (via u-boot).


 That's all for now. I'll be around!

 /cmr
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQEcBAEBCAAGBQJWMGckAAoJEJkCeK12JDMUHGIH/0g9K7ksjuF/Sn1t16f+nods
 DiB59xRSCKYwGa+y6CUXTqLaRKkpS+RkXW5w4egBAa8r8m2c1+/D5qFJkjZIxnSh
 J7aBxK8xto5bno3dngn3KchtvUVD7P0jQi20GFrX9IobriGEzxERJs+uc9VBmlxW
 zTobtXDvIlFbUM/0Dl7xSaH748QikvqaR+WaADZPNAcZQ3ui/HpDqZCVSt771HnH
 WzMennnstmZPw8/GRP1AkOEPgh8VTXwzsqYFtxSOqddi4zQJeyEJW/nu0ReQCLIa
 LdbGewTOZutC9/nw73O1c+LeDTC5TUzUwnc11MwYxCYLjbiSkCGWZHVYUsgyBK4=
 =Ph57
 -----END PGP SIGNATURE-----


 From corey at octayn.net  Sat Sep 26 16:09:39 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 26 Sep 2015 16:09:39 -0400
 Subject: sel4-sys actually done now! And online docs.
 Message-ID: <1443298179.2053097.394342753.0F3C8575@webmail.messagingengine.com>

 So the "bug" in rustc was not as much of a bug as an implementation annoyance.
 Can't use gcc-style constraints in inline assembly. Simple enough fix, just name all
 the registers explicitly. I've published version 0.0.3 to crates.io. It should work, it
 at least compiles! I've got a number of other things to do this weekend. I might get
 back to it on Monday for the high-level bindings and initial thread boostrap.

 I've put rustdocs up at https://doc.robigalia.org/. Once we have CI up and going
 (probably GitLab CI), the docs will be automatically uploaded.

 -- 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1443298179.2053097.394342753.0F3C8575%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Tue Sep 22 22:06:13 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 22 Sep 2015 22:06:13 -0400
 Subject: ARM development boards
 Message-ID: <1442973973.4047402.391064329.25DFB6BD@webmail.messagingengine.com>

 I've purchased a HiKey (64-bit Cortex-A53)  and Sabre Lite  (32-bit freescale i.MX6) to have. The Sabre Lite is officially supported by seL4 as a verified platform afaict. Should be able to play with it soon! 

 -- 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442973973.4047402.391064329.25DFB6BD%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Tue Sep 22 01:16:33 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 22 Sep 2015 01:16:33 -0400
 Subject: Status
 Message-ID: <1442898993.3055172.390097025.59AB2779@webmail.messagingengine.com>

 Graham and I spent some time tonight taking a deepr look at seL4 and finished up rust-seL4 for x86. Unfortunately, we hit a rustc inline assembly bug, which I'm looking into reducing and fixing. In the meantime, can whip up a workaround by invoking actual assembly. It does incur a performance hit due to function call overhead but it's temporary I hope. One step closer to "f".

 Baha volunteered to look into minix to figure out process state. Killian is porting rust-seL4 to arm. Graham is working on a page allocator. Someone will need to write an elf loader. There are a few projects for it on github but I have no idea how robust they are. I'll be working on a higher level wrapper around sel4. It would be nice if someone could send a message to the sel4 list inquiring about processor specific extensions, especially support for the floating point unit. 
 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442898993.3055172.390097025.59AB2779%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Mon Sep 21 00:38:46 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 21 Sep 2015 00:38:46 -0400
 Subject: Migration away from repo
 Message-ID: <[email protected]>

 Hey all,

 Sorry for the short notice. Since we aren't using Gerrit, using repo is
 basically pointless. It doesn't know how to handle uploading code to
 non-Gerrit review tools, such as GitLab. So, I've added a script to the
 devbox: `get_new_repos.sh`. Additionally, there is a script
 `add_remotes.sh` which accepts one argument, your gitlab username. If it
 is not given, it will prompt you for it. It will go over each repo that
 `get_new_repos.sh` knows about and if there does not already exist an
 `upstream` remote, it will rename `origin` to `upstream` and add your
 gitlab fork as the `origin`.

 To submit changes, you'll need to `git pull`, `git push` etc as you
 would with any other Git repo project.  You'll need a fork of the repo
 on GitLab which you can then send pull requests from. If you need any
 help figuring that out, let me know.

 To transition, I recommend just deleting your `robigalia` directory
 entirely and cloning the `devbox` repo and doing another `vagrant up`.
 For ease of use, I also recommand setting up SSH key authentication
 with GitLab. Their docs: http://doc.gitlab.com/ce/ssh/README.html.
 I've enabled "SSH agent forwarding" for the VM. This means that any
 SSH keys you have *will* be exposed to the VM if you are running
 and SSH agent (which you probably should be! they're convenient).
 I don't think there are any security concerns here, but SSH agent
 forwarding in general carries some risks. Some more details:
 https://heipei.github.io/2015/02/26/SSH-Agent-Forwarding-considered-harmful/

 Previously, provisioning a fresh VM would take a very long time due to
 the large downloads. I've managed to slim those down by about 1GB, but
 the Rust download still takes a fair amount of time.

 I didn't get much done this weekend due to health issues.

 --
 /cmr



 From corey at octayn.net  Sat Sep 19 00:48:39 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 19 Sep 2015 00:48:39 -0400
 Subject: seL4 Roadmap
 Message-ID: <1442638119.2212412.387867089.5507A2C7@webmail.messagingengine.com>

 If you didn't see it, the seL4 project published a roadmap:
 <http://sel4.systems/Info/Roadmap/>.

 I encourage you to sign up for the seL4 mailing lists. They're
 pretty low-traffic overall.

 -- 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442638119.2212412.387867089.5507A2C7%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Sat Sep 19 00:44:28 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 19 Sep 2015 00:44:28 -0400
 Subject: Official Project Kickoff Thing?
 Message-ID: <1442637867.2210963.387829729.448EA0E6@webmail.messagingengine.com>

 Hey all,

 I've settled on the initial infrastructure we'll use for the project.
 For now, we won't use mantisbt or gerrit (the tools hosted on
 robigalia.org), and instead use the tools that Gitlab provides. They
 aren't ideal, but I'm sick of fighting with the servers.

 >From here on out, I hope we can send out emails to coordinate changes
 and so forth. Here's the situation right now:

 - We're using the repo tool
  (https://source.android.com/source/using-repo.html,
  https://source.android.com/source/downloading.html#installing-repo) to
  manage the tree of repositories that we are bound to accumulate.

 - There are repos on https://gitlab.com/robigalia with the current work.

 - We are using Vagrant (https://www.vagrantup.com/) as the "standardized
  development environment". https://gitlab.com/robigalia/manifest has
  instructions for how to get setup.

 - Graham and I have almost finished the lowest level library, rust-sel4,
  for talking to the kernel. Killian was voluntold to port it to ARM. In
  theory by tomorrow I'll have a Rust application (buildable and
  runnable inside Vagrant) that prints "f", on x86. Once I've got
  that I'll look at a cross-compiler to ARM.

 The next conceptual thing that needs doing is designing how processes
 will communicate. The two basic options are going through a broker
 thread over IPC for everything, or directly modeling the POSIX API with
 capabilities. There are a few reasons it will be hard to use caps for
 everything, the biggest being CLOEXEC and fd inheritance. So there will
 need to be some amount of involvement with a broker thread. Will need to
 carefully comb the Linux source (in or around `struct task`) and the
 POSIX spec. MINIX is probably better to study than Linux, since it's
 designed for simplicity, but I'm unfamiliar with it. Anyone want
 to volunteer to study MINIX and gather some requirements
 for the process structure?

 We'll also need to write a page allocator and a malloc on top of that.
 We could use jemalloc but I find the idea of a pure-Rust allocator
 very appealing. We could port jemalloc, or perhaps simpler,
 https://github.com/thestinger/allocator/. Unfortunately Daniel's impl
 uses jemalloc's red-black tree, which is nice because it's
 highly optimized but it's not as nice because it's pretty complex.
 We'll want to look forward to efficient multithreading, and
 not use an allocator designed for a single-core. Does anyone
 want to volunteer to do that? This would be pretty straightforward
 to prototype on a desktop, by calling mmap() (which is basically
 what the page allocator does - implement mmap).

 --
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442637867.2210963.387829729.448EA0E6%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Sat Sep 26 16:09:39 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 26 Sep 2015 16:09:39 -0400
 Subject: sel4-sys actually done now! And online docs.
 Message-ID: <1443298179.2053097.394342753.0F3C8575@webmail.messagingengine.com>

 So the "bug" in rustc was not as much of a bug as an implementation annoyance.
 Can't use gcc-style constraints in inline assembly. Simple enough fix, just name all
 the registers explicitly. I've published version 0.0.3 to crates.io. It should work, it
 at least compiles! I've got a number of other things to do this weekend. I might get
 back to it on Monday for the high-level bindings and initial thread boostrap.

 I've put rustdocs up at https://doc.robigalia.org/. Once we have CI up and going
 (probably GitLab CI), the docs will be automatically uploaded.

 -- 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1443298179.2053097.394342753.0F3C8575%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Tue Sep 22 22:06:13 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 22 Sep 2015 22:06:13 -0400
 Subject: ARM development boards
 Message-ID: <1442973973.4047402.391064329.25DFB6BD@webmail.messagingengine.com>

 I've purchased a HiKey (64-bit Cortex-A53)  and Sabre Lite  (32-bit freescale i.MX6) to have. The Sabre Lite is officially supported by seL4 as a verified platform afaict. Should be able to play with it soon! 

 -- 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442973973.4047402.391064329.25DFB6BD%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Tue Sep 22 01:16:33 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 22 Sep 2015 01:16:33 -0400
 Subject: Status
 Message-ID: <1442898993.3055172.390097025.59AB2779@webmail.messagingengine.com>

 Graham and I spent some time tonight taking a deepr look at seL4 and finished up rust-seL4 for x86. Unfortunately, we hit a rustc inline assembly bug, which I'm looking into reducing and fixing. In the meantime, can whip up a workaround by invoking actual assembly. It does incur a performance hit due to function call overhead but it's temporary I hope. One step closer to "f".

 Baha volunteered to look into minix to figure out process state. Killian is porting rust-seL4 to arm. Graham is working on a page allocator. Someone will need to write an elf loader. There are a few projects for it on github but I have no idea how robust they are. I'll be working on a higher level wrapper around sel4. It would be nice if someone could send a message to the sel4 list inquiring about processor specific extensions, especially support for the floating point unit. 
 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442898993.3055172.390097025.59AB2779%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Mon Sep 21 00:38:46 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 21 Sep 2015 00:38:46 -0400
 Subject: Migration away from repo
 Message-ID: <[email protected]>

 Hey all,

 Sorry for the short notice. Since we aren't using Gerrit, using repo is
 basically pointless. It doesn't know how to handle uploading code to
 non-Gerrit review tools, such as GitLab. So, I've added a script to the
 devbox: `get_new_repos.sh`. Additionally, there is a script
 `add_remotes.sh` which accepts one argument, your gitlab username. If it
 is not given, it will prompt you for it. It will go over each repo that
 `get_new_repos.sh` knows about and if there does not already exist an
 `upstream` remote, it will rename `origin` to `upstream` and add your
 gitlab fork as the `origin`.

 To submit changes, you'll need to `git pull`, `git push` etc as you
 would with any other Git repo project.  You'll need a fork of the repo
 on GitLab which you can then send pull requests from. If you need any
 help figuring that out, let me know.

 To transition, I recommend just deleting your `robigalia` directory
 entirely and cloning the `devbox` repo and doing another `vagrant up`.
 For ease of use, I also recommand setting up SSH key authentication
 with GitLab. Their docs: http://doc.gitlab.com/ce/ssh/README.html.
 I've enabled "SSH agent forwarding" for the VM. This means that any
 SSH keys you have *will* be exposed to the VM if you are running
 and SSH agent (which you probably should be! they're convenient).
 I don't think there are any security concerns here, but SSH agent
 forwarding in general carries some risks. Some more details:
 https://heipei.github.io/2015/02/26/SSH-Agent-Forwarding-considered-harmful/

 Previously, provisioning a fresh VM would take a very long time due to
 the large downloads. I've managed to slim those down by about 1GB, but
 the Rust download still takes a fair amount of time.

 I didn't get much done this weekend due to health issues.

 --
 /cmr



 From corey at octayn.net  Sat Sep 19 00:48:39 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 19 Sep 2015 00:48:39 -0400
 Subject: seL4 Roadmap
 Message-ID: <1442638119.2212412.387867089.5507A2C7@webmail.messagingengine.com>

 If you didn't see it, the seL4 project published a roadmap:
 <http://sel4.systems/Info/Roadmap/>.

 I encourage you to sign up for the seL4 mailing lists. They're
 pretty low-traffic overall.

 -- 
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442638119.2212412.387867089.5507A2C7%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.



 From corey at octayn.net  Sat Sep 19 00:44:28 2015
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 19 Sep 2015 00:44:28 -0400
 Subject: Official Project Kickoff Thing?
 Message-ID: <1442637867.2210963.387829729.448EA0E6@webmail.messagingengine.com>

 Hey all,

 I've settled on the initial infrastructure we'll use for the project.
 For now, we won't use mantisbt or gerrit (the tools hosted on
 robigalia.org), and instead use the tools that Gitlab provides. They
 aren't ideal, but I'm sick of fighting with the servers.

 >From here on out, I hope we can send out emails to coordinate changes
 and so forth. Here's the situation right now:

 - We're using the repo tool
  (https://source.android.com/source/using-repo.html,
  https://source.android.com/source/downloading.html#installing-repo) to
  manage the tree of repositories that we are bound to accumulate.

 - There are repos on https://gitlab.com/robigalia with the current work.

 - We are using Vagrant (https://www.vagrantup.com/) as the "standardized
  development environment". https://gitlab.com/robigalia/manifest has
  instructions for how to get setup.

 - Graham and I have almost finished the lowest level library, rust-sel4,
  for talking to the kernel. Killian was voluntold to port it to ARM. In
  theory by tomorrow I'll have a Rust application (buildable and
  runnable inside Vagrant) that prints "f", on x86. Once I've got
  that I'll look at a cross-compiler to ARM.

 The next conceptual thing that needs doing is designing how processes
 will communicate. The two basic options are going through a broker
 thread over IPC for everything, or directly modeling the POSIX API with
 capabilities. There are a few reasons it will be hard to use caps for
 everything, the biggest being CLOEXEC and fd inheritance. So there will
 need to be some amount of involvement with a broker thread. Will need to
 carefully comb the Linux source (in or around `struct task`) and the
 POSIX spec. MINIX is probably better to study than Linux, since it's
 designed for simplicity, but I'm unfamiliar with it. Anyone want
 to volunteer to study MINIX and gather some requirements
 for the process structure?

 We'll also need to write a page allocator and a malloc on top of that.
 We could use jemalloc but I find the idea of a pure-Rust allocator
 very appealing. We could port jemalloc, or perhaps simpler,
 https://github.com/thestinger/allocator/. Unfortunately Daniel's impl
 uses jemalloc's red-black tree, which is nice because it's
 highly optimized but it's not as nice because it's pretty complex.
 We'll want to look forward to efficient multithreading, and
 not use an allocator designed for a single-core. Does anyone
 want to volunteer to do that? This would be pretty straightforward
 to prototype on a desktop, by calling mmap() (which is basically
 what the page allocator does - implement mmap).

 --
 /cmr

 -- 
 You received this message because you are subscribed to the Google Groups "robigalia-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send an email to robigalia-dev+unsubscribe at googlegroups.com.
 To post to this group, send email to robigalia-dev at googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/robigalia-dev/1442637867.2210963.387829729.448EA0E6%40webmail.messagingengine.com.
 For more options, visit https://groups.google.com/d/optout.


 From corey at octayn.net  Fri Apr  1 13:02:15 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 2 Apr 2016 04:02:15 +1100
 Subject: [robigalia-dev] Suggestion: add news page / blog
 In-Reply-To: <[email protected]>
 References: <[email protected]>
 Message-ID: <[email protected]>

 On Thu, Mar 31, 2016 at 10:08:24PM +0200, Ernst Rohlicek wrote:
 > Greetings, I find the idea of seL4 + Rust + Linux compatibility
 > intriguing and would like to follow your project.
 > 
 > Please add a news page, or better, a small blog - with Atom/RSS rews
 > feed for publishing activity.
 > 

 This is on my radar as something that needs doing, but I haven't done it yet
 because there is not yet anything worth widely reporting. Progress right now
 is slow, due to my limited time at the moment, but continues incrementally. I
 send emails to this list with development updates as they happen.

 -- 
 cmr
 +610481762084
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160402/e7a0a54e/attachment.asc>

 From corey at octayn.net  Fri Apr  1 13:02:15 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 2 Apr 2016 04:02:15 +1100
 Subject: [robigalia-dev] Suggestion: add news page / blog
 In-Reply-To: <[email protected]>
 References: <[email protected]>
 Message-ID: <[email protected]>

 On Thu, Mar 31, 2016 at 10:08:24PM +0200, Ernst Rohlicek wrote:
 > Greetings, I find the idea of seL4 + Rust + Linux compatibility
 > intriguing and would like to follow your project.
 > 
 > Please add a news page, or better, a small blog - with Atom/RSS rews
 > feed for publishing activity.
 > 

 This is on my radar as something that needs doing, but I haven't done it yet
 because there is not yet anything worth widely reporting. Progress right now
 is slow, due to my limited time at the moment, but continues incrementally. I
 send emails to this list with development updates as they happen.

 -- 
 cmr
 +610481762084
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160402/e7a0a54e/attachment.asc>
 From corey at octayn.net  Sun Dec 25 13:46:36 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sun, 25 Dec 2016 13:46:36 -0500
 Subject: [robigalia-dev] Logo, blog
 Message-ID: <[email protected]>

 Long time no mailing list update! We now have a logo:

 https://gitlab.com/robigalia/meta/blob/master/logo.svg

 And a blog:

 https://robigalia.org/blog/

 There's also a twitter account where I blast short updates:

 http://twitter.com/robigalia_proj

 Best,
 -- 
 cmr
 http://octayn.net/
 +16038524272

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 488 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20161225/9516ae33/attachment.asc>

 From corey at octayn.net  Sun Dec 25 13:46:36 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sun, 25 Dec 2016 13:46:36 -0500
 Subject: [robigalia-dev] Logo, blog
 Message-ID: <[email protected]>

 Long time no mailing list update! We now have a logo:

 https://gitlab.com/robigalia/meta/blob/master/logo.svg

 And a blog:

 https://robigalia.org/blog/

 There's also a twitter account where I blast short updates:

 http://twitter.com/robigalia_proj

 Best,
 -- 
 cmr
 http://octayn.net/
 +16038524272

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 488 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20161225/9516ae33/attachment.asc>
 From corey at octayn.net  Sat Jan  2 07:36:43 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 2 Jan 2016 07:36:43 -0500
 Subject: [robigalia-dev] Today's status: rust-sel4
 Message-ID: <20160102123643.GA20171@roger>

 Hi all,

 It's finally started happening. I used to write "self" instead of "sel4", and
 now I'm writing "sel4" instead of "self". Send help.

 In other news, the first draft of rust-sel4 is pushed to
 https://gitlab.com/robigalia/rust-sel4

 This is the basic high-level interface to kernel objects, but there's still
 some more work to do for object allocation. I did an inspection of sel4-sys
 and found a number of silly bugs and even a missing syscall (NBRecv).

 The next thing to do code-wise is define some more opinionated interfaces to
 start creating the "personality" for Robigalia. I'm not quite sure how I want
 it to feel yet. I'll tinker around with some ideas.

 However, the next thing I'm going to work on is documentation. I want to
 polish up the READMEs and crate documentation, and start on some small
 examples using each of the crates.

 I'm going to document setting up a Rust
 environment for cross-compiling without using the Vagrant VM.

 I'm going to rewrite the README for the devbox.

 I'm going to create the homepage for good this time, maybe not with much content yet.

 I'm planning a series of documents introducing newcomers to microkernels,
 osdev, seL4, Rust, and the combination of the four. They might published as a
 blog post of some kind, although I really dislike the blog-post format for
 that sort of thing.  They'll probably end up as files in meta.

 I've also updated doc.robigalia.org. It needs a nicer index page, ideally
 generated from the list of crates, though I'll probably put that off until CI.

 Until next time,
 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160102/aad7251c/attachment.asc>

 From grahamnorthup at yahoo.com  Sat Jan  2 15:31:27 2016
 From: grahamnorthup at yahoo.com (Graham Northup)
 Date: Sat, 2 Jan 2016 15:31:27 -0500
 Subject: [robigalia-dev] Today's status: rust-sel4
 In-Reply-To: <20160102123643.GA20171@roger>
 References: <20160102123643.GA20171@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 "sel4" and "seL4" are such PITAs to type :P

 All of that sounds actually fun; let me know if I can help in some
 silly way!

 Thanks,
 Graham

 On 01/02/2016 07:36 AM, Corey Richardson wrote:
 > Hi all,
 > 
 > It's finally started happening. I used to write "self" instead of
 > "sel4", and now I'm writing "sel4" instead of "self". Send help.
 > 
 > In other news, the first draft of rust-sel4 is pushed to 
 > https://gitlab.com/robigalia/rust-sel4
 > 
 > This is the basic high-level interface to kernel objects, but
 > there's still some more work to do for object allocation. I did an
 > inspection of sel4-sys and found a number of silly bugs and even a
 > missing syscall (NBRecv).
 > 
 > The next thing to do code-wise is define some more opinionated
 > interfaces to start creating the "personality" for Robigalia. I'm
 > not quite sure how I want it to feel yet. I'll tinker around with
 > some ideas.
 > 
 > However, the next thing I'm going to work on is documentation. I
 > want to polish up the READMEs and crate documentation, and start on
 > some small examples using each of the crates.
 > 
 > I'm going to document setting up a Rust environment for
 > cross-compiling without using the Vagrant VM.
 > 
 > I'm going to rewrite the README for the devbox.
 > 
 > I'm going to create the homepage for good this time, maybe not with
 > much content yet.
 > 
 > I'm planning a series of documents introducing newcomers to
 > microkernels, osdev, seL4, Rust, and the combination of the four.
 > They might published as a blog post of some kind, although I really
 > dislike the blog-post format for that sort of thing.  They'll
 > probably end up as files in meta.
 > 
 > I've also updated doc.robigalia.org. It needs a nicer index page,
 > ideally generated from the list of crates, though I'll probably put
 > that off until CI.
 > 
 > Until next time, -- cmr +16032392210 http://octayn.net/
 > 
 > 
 > 
 > _______________________________________________ robigalia-dev
 > mailing list robigalia-dev at lists.robigalia.org 
 > http://lists.robigalia.org/listinfo/robigalia-dev
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWiDOYAAoJEF0ADm9Tk3b7LOMQAL+jpcSE2UqaVNf2wi0zdZzw
 Bu3GaG8zDmFdSFUSblIw+4iTg6tqbDOYJPs9jewwU0+wgmetlutxMCa+fyHj+lGm
 8mrGVRRvOeMGC/bfiG5NHL9khO5xzltdVUNA35Ipbj32Lov2rpMQa6XN87UZ4CzT
 UBxcmEzls07sok7EdKJQGcNhZpQw5b7Bvg9tTLHUYUi9RI6oGjrfTfxpkfB+T0KJ
 deBiICKoIjdLmI85YJ7SLon/lM9OAZX3vwj5Z0e/f+mk1OE+BbJTc2AsuMiL9UMx
 FHhezHsGfjdfp3xp6o6Tkbvj7vdd0HBUj928P7dvLTF8sY8y7D4Dm5/BxaiJO/Qj
 W/85oTY4fMvlH8NfkTeeboiuFXmOHIM9OkUZuX0cx3gpZsxlI7PU4JoUhMWoxGhK
 dreq9UwGHUFdim57hXTmMyxc45fM09xsUw2XC4OinQNrMstR7IbqKY4s5EhOFfQg
 Y27+wRyr1tjC8vzO04WVYVNRyaikGZSbiQhk7KKVeuTn72gpexxCPCdt+vOwvLiv
 qtS8wLTjd7CXgm4A3o42hO+phN3Ak8G+lAq26QUhCcU+91ivwUimDwxxloW6DBcO
 Qy3gbiixBKmq3flwYwhWcdxffHHmly0SWC4VX0Md+xCxXB8V5Jpq+ddHgD4AHP70
 Z6+mgehHLRZwq369yM+r
 =4S2p
 -----END PGP SIGNATURE-----


 From corey at octayn.net  Mon Jan  4 04:35:06 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 4 Jan 2016 04:35:06 -0500
 Subject: [robigalia-dev] GitLab CI!
 Message-ID: <20160104093506.GA7909@roger>

 Hi all,

 I just finished setting up GitLab CI for all the repos that have code in them.
 For now, repos are just setup to build. Setting up tests is going to be a bit
 harder since they need to run in VM. cargo's built-in test support is useless
 because of that.

 The neat thing about GitLab CI compared to other services is that we can set
 up and run our own build servers. The config for the one I'm running now is in
 this repo:

 https://gitlab.com/robigalia/runner

 You shouldn't need to do anything with that, though.

 Here's an example build screen for a commit:

 https://gitlab.com/robigalia/sel4-sys/builds/514397

 and here's the canonical project config:

 https://gitlab.com/robigalia/sel4-sys/blob/master/.gitlab-ci.yml

 It's really unfortunate that these yaml files are duplicated all over the
 place. I don't have a good solution to that yet. Somewhat ironically, this is
 a feature that repo has that would have been really convenient :)

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160104/28335927/attachment.asc>

 From corey at octayn.net  Mon Jan  4 04:41:28 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 4 Jan 2016 04:41:28 -0500
 Subject: [robigalia-dev] Targets moved, update your build environments!
 Message-ID: <20160104094128.GB7909@roger>

 Hi all,

 I split out target files from sel4-sys into a new repo:

 https://gitlab.com/robigalia/sel4-targets

 They didn't really belong with the code in sel4-sys.

 If you're using the Vagrant VM, do `vagrant destroy && vagrant up` after
 pulling the latest changes.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160104/06b9303d/attachment.asc>

 From corey at octayn.net  Tue Jan  5 00:56:04 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 00:56:04 -0500
 Subject: [robigalia-dev] New site,
 	what examples/tutorials do you want to see?
 Message-ID: <20160105055604.GA32723@roger>

 New site is up: https://robigalia.org/

 Any and all feedback (content, style) requested.

 Source is at:

 https://gitlab.com/robigalia/meta/tree/master/docs

 In particular note the new content,

 https://robigalia.org/build-environment.html

 https://robigalia.org/contributing.html

 Next up, copying that CONTRIBUTING.md all over the damn place, and come up
 with a LICENSE file so gitlab stops bugging me.

 READMEs still need to be edited (and one written for the devbox), tutorials
 need to be written, and example code needs to be written.

 I need to expand the introduction to have a brief background on microkernels,
 Rust, and seL4.

 What examples/tutorials would you like to see? I plan on writing a crate for
 using the x86 VGA framebuffer and an example using that. I also want to port
 the official sel4 tutorials, though not CAmkES:

 https://github.com/seL4-projects/sel4-tutorials

 Once that's done, it's time to announce! This will involve a post to the sel4
 mailing list, hacker news, the rust subreddit, and the rust community forums.
 I expect it to make a small "plish" with decent reception (read: upvotes) and
 no new contributors, but a lot of interest in where the project goes.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/68deed60/attachment.asc>

 From coddinkn at clarkson.edu  Tue Jan  5 09:38:30 2016
 From: coddinkn at clarkson.edu (Killian Coddington)
 Date: Tue, 5 Jan 2016 09:38:30 -0500
 Subject: [robigalia-dev] New site,
 	what examples/tutorials do you want to see?
 In-Reply-To: <20160105055604.GA32723@roger>
 References: <20160105055604.GA32723@roger>
 Message-ID: <CAETVt1wSr8w+OJUzWUBb_iOgqO+tT76wttreeMJchNq+f_-+Fg@mail.gmail.com>

 rust,

 The new site is nice both aesthetics and functionally. I like the simpe
 white with black text but not hideous look. I would like to start
 contributing again and in a hopefully more significant capacity.

 I know one of your previous emails mentioned a java script demo, I am
 uncertain I understand exactly what that would be but Im willing to take
 that on as it seems like a fairly well defined/self-contained task, I just
 might need some clarification about it.

 After completing that in a (hopefully) somewhat timely fashion I'd like to
 continue contributing as much as I can, this project seems cool and like a
 great learning opportunity and I don't want to miss being involved due to
 lazy.

 Let me know if there is anything else you think I could be helpful with,
 and again good job with the site. Also feel free to harrass me (of course
 in compliance with the code of conduct) about contributing or failing to
 stay involved at least in knowing whats going on.

 Thanks,
 Killian


 On Tue, Jan 5, 2016 at 12:56 AM, Corey Richardson <corey at octayn.net> wrote:

 > New site is up: https://robigalia.org/
 >
 > Any and all feedback (content, style) requested.
 >
 > Source is at:
 >
 > https://gitlab.com/robigalia/meta/tree/master/docs
 >
 > In particular note the new content,
 >
 > https://robigalia.org/build-environment.html
 >
 > https://robigalia.org/contributing.html
 >
 > Next up, copying that CONTRIBUTING.md all over the damn place, and come up
 > with a LICENSE file so gitlab stops bugging me.
 >
 > READMEs still need to be edited (and one written for the devbox), tutorials
 > need to be written, and example code needs to be written.
 >
 > I need to expand the introduction to have a brief background on
 > microkernels,
 > Rust, and seL4.
 >
 > What examples/tutorials would you like to see? I plan on writing a crate
 > for
 > using the x86 VGA framebuffer and an example using that. I also want to
 > port
 > the official sel4 tutorials, though not CAmkES:
 >
 > https://github.com/seL4-projects/sel4-tutorials
 >
 > Once that's done, it's time to announce! This will involve a post to the
 > sel4
 > mailing list, hacker news, the rust subreddit, and the rust community
 > forums.
 > I expect it to make a small "plish" with decent reception (read: upvotes)
 > and
 > no new contributors, but a lot of interest in where the project goes.
 >
 > --
 > cmr
 > +16032392210
 > http://octayn.net/
 >
 > _______________________________________________
 > robigalia-dev mailing list
 > robigalia-dev at lists.robigalia.org
 > http://lists.robigalia.org/listinfo/robigalia-dev
 >
 >
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/102fdce6/attachment.html>

 From corey at octayn.net  Tue Jan  5 10:17:23 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 10:17:23 -0500
 Subject: [robigalia-dev] New site,
 what examples/tutorials do you want to see?
 In-Reply-To: <CAETVt1wSr8w+OJUzWUBb_iOgqO+tT76wttreeMJchNq+f_-+Fg@mail.gmail.com>
 References: <20160105055604.GA32723@roger>
 <CAETVt1wSr8w+OJUzWUBb_iOgqO+tT76wttreeMJchNq+f_-+Fg@mail.gmail.com>
 Message-ID: <20160105151723.GA6893@roger>

 On Tue, Jan 05, 2016 at 09:38:30AM -0500, Killian Coddington wrote:
 > rust,
 >
 > The new site is nice both aesthetics and functionally. I like the simpe
 > white with black text but not hideous look. I would like to start
 > contributing again and in a hopefully more significant capacity.
 >

 Good to hear!

 > I know one of your previous emails mentioned a java script demo, I am
 > uncertain I understand exactly what that would be but Im willing to take
 > that on as it seems like a fairly well defined/self-contained task, I just
 > might need some clarification about it.
 >

 I've added some more details to the issue, and assigned you to it:

 https://gitlab.com/robigalia/meta/issues/2

 Bop me in that thread or on IRC for clarifications :)

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/ee27c799/attachment.asc>

 From corey at octayn.net  Tue Jan  5 16:19:01 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 16:19:01 -0500
 Subject: [robigalia-dev] new website pages, devbox docs
 Message-ID: <20160105211901.GA17711@roger>

 Three new pages, dashboard thanks to feedback from Adam.

 devbox: https://gitlab.com/robigalia/devbox

 If you want to use the devbox and have an old one lying around, I recommend
 nuking it from orbit with an rm -rf and cloning anew.

 Dashboard: https://robigalia.org/dashboard.html

 Why Rust?: https://robigalia.org/why-rust.html

 About microkernels: https://robigalia.org/about-microkernels.html

 Somewhat fluff right now, but potentially useful to help explain what we're
 about.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/0113e983/attachment.asc>

 From corey at octayn.net  Tue Jan  5 16:44:39 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 16:44:39 -0500
 Subject: [robigalia-dev] Issues opened on various repos
 Message-ID: <20160105214439.GB17711@roger>

 Hi all,

 I've opened issues on most of the crates for things that need doing.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/d25aed59/attachment.asc>

 From corey at octayn.net  Tue Jan  5 22:48:45 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 22:48:45 -0500
 Subject: [robigalia-dev] Release date: 2016-01-12T09:00:00-0500
 Message-ID: <20160106034845.GB20089@roger>

 I'm hoping to have everything cemented down and ready to go by this Sunday,
 with the intention of launching 2016-01-12T09:00:00-0500. If ARM and the
 Javascript-based VM are ready by then, that'd be lovely, if not, that's OK
 too.

 Here's a draft of the email that will go out:

 ========

 On behalf of the Robigalia project I am pleased to announce our first public
 release of the core libraries for using Rust on seL4. Currently, this consists
 of a raw interface akin to libsel4 and a higher-level "Rustic" interface.
 Currently, only x86 is supported. An ARM port is in progress.

 We have a website: https://robigalia.org/
 And a mailing list: https://lists.robigalia.org/listinfo/robigalia-dev

 We have a tutorial modeled after the sel4-tutorials presentation:

 https://robigalia.org/tutorial.html

 As well as some example drivers and code:

 https://robigalia.org/examples.html

 The goal of the Robigalia project is to promote Rust as a robust choice for
 application development on seL4 and has the long-term goal of producing
 Robigo, a POSIX-compatible personality. We're in the initial stages of
 development. We are primarily a group of students from Clarkson University.

 ========


 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/c414d924/attachment.asc>

 From corey at octayn.net  Wed Jan  6 18:17:28 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 6 Jan 2016 18:17:28 -0500
 Subject: [robigalia-dev] We've been posted to HN
 Message-ID: <20160106231728.GA31605@roger>

 Currently on the front page. I'm sad that it was so early, another week of
 docs, tutorials, and working on the high-level interface was going to make for
 a very polished initial release.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160106/dc3aac00/attachment.asc>

 From corey at octayn.net  Wed Jan  6 23:13:38 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 6 Jan 2016 23:13:38 -0500
 Subject: [robigalia-dev] Today's progress
 Message-ID: <20160107041338.GA32135@roger>

 Hi all,

 Added a script for making an index for the doc page, see it in action:

 https://doc.robigalia.org/

 I need to tweak some stuff on the server before doc building + uploads can be
 automatic.

 Added some missing stuff to sel4-sys, published a new version of it and
 sel4-start. Added object allocation interface to rust-sel4, but no
 implementation yet. Started looking at the sel4 userspace libs for inspiration
 on what implementations should be supported initially.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160106/ed721b04/attachment.asc>

 From corey at octayn.net  Thu Jan  7 08:03:35 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Thu, 7 Jan 2016 08:03:35 -0500
 Subject: [robigalia-dev] We've been posted to HN
 In-Reply-To: <20160106231728.GA31605@roger>
 Message-ID: <20160107130335.GA8944@roger>

 For those that didn't see it, the link is

 https://news.ycombinator.com/item?id=10848890

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160107/e63fcebd/attachment.asc>

 From corey at octayn.net  Fri Jan  8 09:03:49 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 8 Jan 2016 09:03:49 -0500
 Subject: [robigalia-dev] Read-only repo mirrors on github
 Message-ID: <20160108140348.GC10324@roger>

 Based on some feedback on reddit, I've made read-only mirrors of our repos on
 github:

 https://github.com/robigalia

 There's a script in the devbox for doing the mirroring, I have it on a cron
 job to run it daily right now.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160108/0189855c/attachment.asc>

 From kmarsh386 at gmail.com  Sat Jan 23 16:23:27 2016
 From: kmarsh386 at gmail.com (Kyle Marsh)
 Date: Sat, 23 Jan 2016 16:23:27 -0500
 Subject: [robigalia-dev] Question on formal verification and whether there
 are plans to change the name
 Message-ID: <CADrbce1v=Fts7tC_qx7ccWXLtyQoFxeeN170wgd_9Kx+nt0eOg@mail.gmail.com>

 Hey there,

 Greatly interested, two questions:

 1. Are there plans to design / segment Robigalia around the ability to
 ultimately formally verify (at least to a limited extent) additional system
 components beyond the microkernel? Or is that more of a "nice to have if
 it's possible later/non-goal of project" kind of thing

 2. The name Robigalia - I'll be honest, it's basically right now why I'm
 not interested in contributing. A project whose name seems to mean "dog
 sacrifice" as it's hard to imagine the general public ever adopting an OS
 with a name that, if they google, has this, I don't know, weird connotation
 for a tech project.

 I mean, like, it's also something I wouldn't want to tell people I develop
 or have on a t-shirt because then when people google it they'd be like wtf.
 This guy is a real weirdo

 I don't really have any opinion on what the name should be, maybe a contest
 for choosing a new name could be held on the userlist or /r/rust as a way
 to build publicity for the project.
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160123/fd3df8a8/attachment.html>

 From corey at octayn.net  Sun Jan 24 08:14:55 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 25 Jan 2016 00:14:55 +1100
 Subject: [robigalia-dev] Question on formal verification and whether
 there are plans to change the name
 In-Reply-To: <CADrbce1v=Fts7tC_qx7ccWXLtyQoFxeeN170wgd_9Kx+nt0eOg@mail.gmail.com>
 References: <CADrbce1v=Fts7tC_qx7ccWXLtyQoFxeeN170wgd_9Kx+nt0eOg@mail.gmail.com>
 Message-ID: <[email protected]>

 On Sat, Jan 23, 2016 at 04:23:27PM -0500, Kyle Marsh wrote:
 > 1. Are there plans to design / segment Robigalia around the ability to
 > ultimately formally verify (at least to a limited extent) additional system
 > components beyond the microkernel? Or is that more of a "nice to have if
 > it's possible later/non-goal of project" kind of thing
 >

 Yes, this is a large factor in my current thinkings. However, I suspect it
 will take at least 5-6 person months of effort to build a verification
 framework for sequential Rust, let alone concurrent Rust. And assumptions
 about invariants guaranteed by the type system cannot be used, since there's
 no formal proof that the type system is sound. The ability to reason about
 Rust code *at all*, in any proof system, will be a significant undertaking. In
 the short-to-medium term, integrating Rust with CAmkES will be the easiest way
 to get formal guarantees about systems built with Rust. The efforts by the
 RustBelt team will be useful, but results are likely years out. (And also
 in Coq, so an end-to-end proof in some HOL prover would be challenging.)

 I'm currently a "visiting student" at NICTA on the verification team. I'm
 hoping to use the knowledge I learn there to build said verification framework
 for Rust after I leave, potentially as my undergraduate thesis project.

 > 2. The name Robigalia - I'll be honest, it's basically right now why I'm
 > not interested in contributing. A project whose name seems to mean "dog
 > sacrifice" as it's hard to imagine the general public ever adopting an OS
 > with a name that, if they google, has this, I don't know, weird connotation
 > for a tech project.
 >

 That is one of the rites that took place during the festival. I'm somewhat
 open to changing the name of the overall project, but not the name of the
 POSIX component (Robigo), or the lower-level runtime (Phoma). It's all a huge
 pun on wheat rusts. The festival (Robigalia) was celebrated to appease Robigo,
 the goddess of crop disease.

 I've already dumped money on the domain name, though, and it's in all the
 licenses/license headers, as well as the DCO, and the name already has
 recognition in the Rust and seL4 communities. Plus the IRC channel, mailing
 list archives... it'd be an obnoxious migration.

 If the project ever gains popularity, it will be the first or second google
 result and have its own wikipedia article.

 > I mean, like, it's also something I wouldn't want to tell people I develop
 > or have on a t-shirt because then when people google it they'd be like wtf.
 > This guy is a real weirdo
 >

 Seems like someone should edit the wikipedia page to move the mention of that
 particular rite away from the second sentence ;) Really, I'm astonished anyone
 has brought this concern up. Animal (and human) sacrifice is part of our
 heritage, and the mentioned festival is so old by now. Like I said, I'm not
 opposed to changing it, and I don't want to trivialize your concern, but...

 > I don't really have any opinion on what the name should be, maybe a contest
 > for choosing a new name could be held on the userlist or /r/rust as a way
 > to build publicity for the project.
 >

 If we do rename it, it has to be *at least* as punny. It took us a few days to
 come up with these names!

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160125/b3ce8f0c/attachment.asc>

 From corey at octayn.net  Sun Jan 24 08:16:51 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 25 Jan 2016 00:16:51 +1100
 Subject: [robigalia-dev] My current status
 Message-ID: <[email protected]>

 Hi all,

 For those of you who I haven't talked to directly, my work on robigalia is
 currently on pause until I iron out some IP "issues" with NICTA.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160125/5f0a6249/attachment.asc>

 From corey at octayn.net  Sat Jan  2 07:36:43 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sat, 2 Jan 2016 07:36:43 -0500
 Subject: [robigalia-dev] Today's status: rust-sel4
 Message-ID: <20160102123643.GA20171@roger>

 Hi all,

 It's finally started happening. I used to write "self" instead of "sel4", and
 now I'm writing "sel4" instead of "self". Send help.

 In other news, the first draft of rust-sel4 is pushed to
 https://gitlab.com/robigalia/rust-sel4

 This is the basic high-level interface to kernel objects, but there's still
 some more work to do for object allocation. I did an inspection of sel4-sys
 and found a number of silly bugs and even a missing syscall (NBRecv).

 The next thing to do code-wise is define some more opinionated interfaces to
 start creating the "personality" for Robigalia. I'm not quite sure how I want
 it to feel yet. I'll tinker around with some ideas.

 However, the next thing I'm going to work on is documentation. I want to
 polish up the READMEs and crate documentation, and start on some small
 examples using each of the crates.

 I'm going to document setting up a Rust
 environment for cross-compiling without using the Vagrant VM.

 I'm going to rewrite the README for the devbox.

 I'm going to create the homepage for good this time, maybe not with much content yet.

 I'm planning a series of documents introducing newcomers to microkernels,
 osdev, seL4, Rust, and the combination of the four. They might published as a
 blog post of some kind, although I really dislike the blog-post format for
 that sort of thing.  They'll probably end up as files in meta.

 I've also updated doc.robigalia.org. It needs a nicer index page, ideally
 generated from the list of crates, though I'll probably put that off until CI.

 Until next time,
 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160102/aad7251c/attachment.asc>

 From grahamnorthup at yahoo.com  Sat Jan  2 15:31:27 2016
 From: grahamnorthup at yahoo.com (Graham Northup)
 Date: Sat, 2 Jan 2016 15:31:27 -0500
 Subject: [robigalia-dev] Today's status: rust-sel4
 In-Reply-To: <20160102123643.GA20171@roger>
 References: <20160102123643.GA20171@roger>
 Message-ID: <[email protected]>

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA256

 "sel4" and "seL4" are such PITAs to type :P

 All of that sounds actually fun; let me know if I can help in some
 silly way!

 Thanks,
 Graham

 On 01/02/2016 07:36 AM, Corey Richardson wrote:
 > Hi all,
 > 
 > It's finally started happening. I used to write "self" instead of
 > "sel4", and now I'm writing "sel4" instead of "self". Send help.
 > 
 > In other news, the first draft of rust-sel4 is pushed to 
 > https://gitlab.com/robigalia/rust-sel4
 > 
 > This is the basic high-level interface to kernel objects, but
 > there's still some more work to do for object allocation. I did an
 > inspection of sel4-sys and found a number of silly bugs and even a
 > missing syscall (NBRecv).
 > 
 > The next thing to do code-wise is define some more opinionated
 > interfaces to start creating the "personality" for Robigalia. I'm
 > not quite sure how I want it to feel yet. I'll tinker around with
 > some ideas.
 > 
 > However, the next thing I'm going to work on is documentation. I
 > want to polish up the READMEs and crate documentation, and start on
 > some small examples using each of the crates.
 > 
 > I'm going to document setting up a Rust environment for
 > cross-compiling without using the Vagrant VM.
 > 
 > I'm going to rewrite the README for the devbox.
 > 
 > I'm going to create the homepage for good this time, maybe not with
 > much content yet.
 > 
 > I'm planning a series of documents introducing newcomers to
 > microkernels, osdev, seL4, Rust, and the combination of the four.
 > They might published as a blog post of some kind, although I really
 > dislike the blog-post format for that sort of thing.  They'll
 > probably end up as files in meta.
 > 
 > I've also updated doc.robigalia.org. It needs a nicer index page,
 > ideally generated from the list of crates, though I'll probably put
 > that off until CI.
 > 
 > Until next time, -- cmr +16032392210 http://octayn.net/
 > 
 > 
 > 
 > _______________________________________________ robigalia-dev
 > mailing list robigalia-dev at lists.robigalia.org 
 > http://lists.robigalia.org/listinfo/robigalia-dev
 > 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2

 iQIcBAEBCAAGBQJWiDOYAAoJEF0ADm9Tk3b7LOMQAL+jpcSE2UqaVNf2wi0zdZzw
 Bu3GaG8zDmFdSFUSblIw+4iTg6tqbDOYJPs9jewwU0+wgmetlutxMCa+fyHj+lGm
 8mrGVRRvOeMGC/bfiG5NHL9khO5xzltdVUNA35Ipbj32Lov2rpMQa6XN87UZ4CzT
 UBxcmEzls07sok7EdKJQGcNhZpQw5b7Bvg9tTLHUYUi9RI6oGjrfTfxpkfB+T0KJ
 deBiICKoIjdLmI85YJ7SLon/lM9OAZX3vwj5Z0e/f+mk1OE+BbJTc2AsuMiL9UMx
 FHhezHsGfjdfp3xp6o6Tkbvj7vdd0HBUj928P7dvLTF8sY8y7D4Dm5/BxaiJO/Qj
 W/85oTY4fMvlH8NfkTeeboiuFXmOHIM9OkUZuX0cx3gpZsxlI7PU4JoUhMWoxGhK
 dreq9UwGHUFdim57hXTmMyxc45fM09xsUw2XC4OinQNrMstR7IbqKY4s5EhOFfQg
 Y27+wRyr1tjC8vzO04WVYVNRyaikGZSbiQhk7KKVeuTn72gpexxCPCdt+vOwvLiv
 qtS8wLTjd7CXgm4A3o42hO+phN3Ak8G+lAq26QUhCcU+91ivwUimDwxxloW6DBcO
 Qy3gbiixBKmq3flwYwhWcdxffHHmly0SWC4VX0Md+xCxXB8V5Jpq+ddHgD4AHP70
 Z6+mgehHLRZwq369yM+r
 =4S2p
 -----END PGP SIGNATURE-----


 From corey at octayn.net  Mon Jan  4 04:35:06 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 4 Jan 2016 04:35:06 -0500
 Subject: [robigalia-dev] GitLab CI!
 Message-ID: <20160104093506.GA7909@roger>

 Hi all,

 I just finished setting up GitLab CI for all the repos that have code in them.
 For now, repos are just setup to build. Setting up tests is going to be a bit
 harder since they need to run in VM. cargo's built-in test support is useless
 because of that.

 The neat thing about GitLab CI compared to other services is that we can set
 up and run our own build servers. The config for the one I'm running now is in
 this repo:

 https://gitlab.com/robigalia/runner

 You shouldn't need to do anything with that, though.

 Here's an example build screen for a commit:

 https://gitlab.com/robigalia/sel4-sys/builds/514397

 and here's the canonical project config:

 https://gitlab.com/robigalia/sel4-sys/blob/master/.gitlab-ci.yml

 It's really unfortunate that these yaml files are duplicated all over the
 place. I don't have a good solution to that yet. Somewhat ironically, this is
 a feature that repo has that would have been really convenient :)

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160104/28335927/attachment.asc>

 From corey at octayn.net  Mon Jan  4 04:41:28 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 4 Jan 2016 04:41:28 -0500
 Subject: [robigalia-dev] Targets moved, update your build environments!
 Message-ID: <20160104094128.GB7909@roger>

 Hi all,

 I split out target files from sel4-sys into a new repo:

 https://gitlab.com/robigalia/sel4-targets

 They didn't really belong with the code in sel4-sys.

 If you're using the Vagrant VM, do `vagrant destroy && vagrant up` after
 pulling the latest changes.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160104/06b9303d/attachment.asc>

 From corey at octayn.net  Tue Jan  5 00:56:04 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 00:56:04 -0500
 Subject: [robigalia-dev] New site,
 	what examples/tutorials do you want to see?
 Message-ID: <20160105055604.GA32723@roger>

 New site is up: https://robigalia.org/

 Any and all feedback (content, style) requested.

 Source is at:

 https://gitlab.com/robigalia/meta/tree/master/docs

 In particular note the new content,

 https://robigalia.org/build-environment.html

 https://robigalia.org/contributing.html

 Next up, copying that CONTRIBUTING.md all over the damn place, and come up
 with a LICENSE file so gitlab stops bugging me.

 READMEs still need to be edited (and one written for the devbox), tutorials
 need to be written, and example code needs to be written.

 I need to expand the introduction to have a brief background on microkernels,
 Rust, and seL4.

 What examples/tutorials would you like to see? I plan on writing a crate for
 using the x86 VGA framebuffer and an example using that. I also want to port
 the official sel4 tutorials, though not CAmkES:

 https://github.com/seL4-projects/sel4-tutorials

 Once that's done, it's time to announce! This will involve a post to the sel4
 mailing list, hacker news, the rust subreddit, and the rust community forums.
 I expect it to make a small "plish" with decent reception (read: upvotes) and
 no new contributors, but a lot of interest in where the project goes.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/68deed60/attachment.asc>

 From coddinkn at clarkson.edu  Tue Jan  5 09:38:30 2016
 From: coddinkn at clarkson.edu (Killian Coddington)
 Date: Tue, 5 Jan 2016 09:38:30 -0500
 Subject: [robigalia-dev] New site,
 	what examples/tutorials do you want to see?
 In-Reply-To: <20160105055604.GA32723@roger>
 References: <20160105055604.GA32723@roger>
 Message-ID: <CAETVt1wSr8w+OJUzWUBb_iOgqO+tT76wttreeMJchNq+f_-+Fg@mail.gmail.com>

 rust,

 The new site is nice both aesthetics and functionally. I like the simpe
 white with black text but not hideous look. I would like to start
 contributing again and in a hopefully more significant capacity.

 I know one of your previous emails mentioned a java script demo, I am
 uncertain I understand exactly what that would be but Im willing to take
 that on as it seems like a fairly well defined/self-contained task, I just
 might need some clarification about it.

 After completing that in a (hopefully) somewhat timely fashion I'd like to
 continue contributing as much as I can, this project seems cool and like a
 great learning opportunity and I don't want to miss being involved due to
 lazy.

 Let me know if there is anything else you think I could be helpful with,
 and again good job with the site. Also feel free to harrass me (of course
 in compliance with the code of conduct) about contributing or failing to
 stay involved at least in knowing whats going on.

 Thanks,
 Killian


 On Tue, Jan 5, 2016 at 12:56 AM, Corey Richardson <corey at octayn.net> wrote:

 > New site is up: https://robigalia.org/
 >
 > Any and all feedback (content, style) requested.
 >
 > Source is at:
 >
 > https://gitlab.com/robigalia/meta/tree/master/docs
 >
 > In particular note the new content,
 >
 > https://robigalia.org/build-environment.html
 >
 > https://robigalia.org/contributing.html
 >
 > Next up, copying that CONTRIBUTING.md all over the damn place, and come up
 > with a LICENSE file so gitlab stops bugging me.
 >
 > READMEs still need to be edited (and one written for the devbox), tutorials
 > need to be written, and example code needs to be written.
 >
 > I need to expand the introduction to have a brief background on
 > microkernels,
 > Rust, and seL4.
 >
 > What examples/tutorials would you like to see? I plan on writing a crate
 > for
 > using the x86 VGA framebuffer and an example using that. I also want to
 > port
 > the official sel4 tutorials, though not CAmkES:
 >
 > https://github.com/seL4-projects/sel4-tutorials
 >
 > Once that's done, it's time to announce! This will involve a post to the
 > sel4
 > mailing list, hacker news, the rust subreddit, and the rust community
 > forums.
 > I expect it to make a small "plish" with decent reception (read: upvotes)
 > and
 > no new contributors, but a lot of interest in where the project goes.
 >
 > --
 > cmr
 > +16032392210
 > http://octayn.net/
 >
 > _______________________________________________
 > robigalia-dev mailing list
 > robigalia-dev at lists.robigalia.org
 > http://lists.robigalia.org/listinfo/robigalia-dev
 >
 >
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/102fdce6/attachment-0001.html>

 From corey at octayn.net  Tue Jan  5 10:17:23 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 10:17:23 -0500
 Subject: [robigalia-dev] New site,
 what examples/tutorials do you want to see?
 In-Reply-To: <CAETVt1wSr8w+OJUzWUBb_iOgqO+tT76wttreeMJchNq+f_-+Fg@mail.gmail.com>
 References: <20160105055604.GA32723@roger>
 <CAETVt1wSr8w+OJUzWUBb_iOgqO+tT76wttreeMJchNq+f_-+Fg@mail.gmail.com>
 Message-ID: <20160105151723.GA6893@roger>

 On Tue, Jan 05, 2016 at 09:38:30AM -0500, Killian Coddington wrote:
 > rust,
 >
 > The new site is nice both aesthetics and functionally. I like the simpe
 > white with black text but not hideous look. I would like to start
 > contributing again and in a hopefully more significant capacity.
 >

 Good to hear!

 > I know one of your previous emails mentioned a java script demo, I am
 > uncertain I understand exactly what that would be but Im willing to take
 > that on as it seems like a fairly well defined/self-contained task, I just
 > might need some clarification about it.
 >

 I've added some more details to the issue, and assigned you to it:

 https://gitlab.com/robigalia/meta/issues/2

 Bop me in that thread or on IRC for clarifications :)

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/ee27c799/attachment.asc>

 From corey at octayn.net  Tue Jan  5 16:19:01 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 16:19:01 -0500
 Subject: [robigalia-dev] new website pages, devbox docs
 Message-ID: <20160105211901.GA17711@roger>

 Three new pages, dashboard thanks to feedback from Adam.

 devbox: https://gitlab.com/robigalia/devbox

 If you want to use the devbox and have an old one lying around, I recommend
 nuking it from orbit with an rm -rf and cloning anew.

 Dashboard: https://robigalia.org/dashboard.html

 Why Rust?: https://robigalia.org/why-rust.html

 About microkernels: https://robigalia.org/about-microkernels.html

 Somewhat fluff right now, but potentially useful to help explain what we're
 about.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/0113e983/attachment.asc>

 From corey at octayn.net  Tue Jan  5 16:44:39 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 16:44:39 -0500
 Subject: [robigalia-dev] Issues opened on various repos
 Message-ID: <20160105214439.GB17711@roger>

 Hi all,

 I've opened issues on most of the crates for things that need doing.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/d25aed59/attachment.asc>

 From corey at octayn.net  Tue Jan  5 22:48:45 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 5 Jan 2016 22:48:45 -0500
 Subject: [robigalia-dev] Release date: 2016-01-12T09:00:00-0500
 Message-ID: <20160106034845.GB20089@roger>

 I'm hoping to have everything cemented down and ready to go by this Sunday,
 with the intention of launching 2016-01-12T09:00:00-0500. If ARM and the
 Javascript-based VM are ready by then, that'd be lovely, if not, that's OK
 too.

 Here's a draft of the email that will go out:

 ========

 On behalf of the Robigalia project I am pleased to announce our first public
 release of the core libraries for using Rust on seL4. Currently, this consists
 of a raw interface akin to libsel4 and a higher-level "Rustic" interface.
 Currently, only x86 is supported. An ARM port is in progress.

 We have a website: https://robigalia.org/
 And a mailing list: https://lists.robigalia.org/listinfo/robigalia-dev

 We have a tutorial modeled after the sel4-tutorials presentation:

 https://robigalia.org/tutorial.html

 As well as some example drivers and code:

 https://robigalia.org/examples.html

 The goal of the Robigalia project is to promote Rust as a robust choice for
 application development on seL4 and has the long-term goal of producing
 Robigo, a POSIX-compatible personality. We're in the initial stages of
 development. We are primarily a group of students from Clarkson University.

 ========


 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160105/c414d924/attachment.asc>

 From corey at octayn.net  Wed Jan  6 18:17:28 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 6 Jan 2016 18:17:28 -0500
 Subject: [robigalia-dev] We've been posted to HN
 Message-ID: <20160106231728.GA31605@roger>

 Currently on the front page. I'm sad that it was so early, another week of
 docs, tutorials, and working on the high-level interface was going to make for
 a very polished initial release.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160106/dc3aac00/attachment.asc>

 From corey at octayn.net  Wed Jan  6 23:13:38 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 6 Jan 2016 23:13:38 -0500
 Subject: [robigalia-dev] Today's progress
 Message-ID: <20160107041338.GA32135@roger>

 Hi all,

 Added a script for making an index for the doc page, see it in action:

 https://doc.robigalia.org/

 I need to tweak some stuff on the server before doc building + uploads can be
 automatic.

 Added some missing stuff to sel4-sys, published a new version of it and
 sel4-start. Added object allocation interface to rust-sel4, but no
 implementation yet. Started looking at the sel4 userspace libs for inspiration
 on what implementations should be supported initially.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160106/ed721b04/attachment.asc>

 From corey at octayn.net  Thu Jan  7 08:03:35 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Thu, 7 Jan 2016 08:03:35 -0500
 Subject: [robigalia-dev] We've been posted to HN
 In-Reply-To: <20160106231728.GA31605@roger>
 Message-ID: <20160107130335.GA8944@roger>

 For those that didn't see it, the link is

 https://news.ycombinator.com/item?id=10848890

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160107/e63fcebd/attachment.asc>

 From corey at octayn.net  Fri Jan  8 09:03:49 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Fri, 8 Jan 2016 09:03:49 -0500
 Subject: [robigalia-dev] Read-only repo mirrors on github
 Message-ID: <20160108140348.GC10324@roger>

 Based on some feedback on reddit, I've made read-only mirrors of our repos on
 github:

 https://github.com/robigalia

 There's a script in the devbox for doing the mirroring, I have it on a cron
 job to run it daily right now.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160108/0189855c/attachment.asc>

 From kmarsh386 at gmail.com  Sat Jan 23 16:23:27 2016
 From: kmarsh386 at gmail.com (Kyle Marsh)
 Date: Sat, 23 Jan 2016 16:23:27 -0500
 Subject: [robigalia-dev] Question on formal verification and whether there
 are plans to change the name
 Message-ID: <CADrbce1v=Fts7tC_qx7ccWXLtyQoFxeeN170wgd_9Kx+nt0eOg@mail.gmail.com>

 Hey there,

 Greatly interested, two questions:

 1. Are there plans to design / segment Robigalia around the ability to
 ultimately formally verify (at least to a limited extent) additional system
 components beyond the microkernel? Or is that more of a "nice to have if
 it's possible later/non-goal of project" kind of thing

 2. The name Robigalia - I'll be honest, it's basically right now why I'm
 not interested in contributing. A project whose name seems to mean "dog
 sacrifice" as it's hard to imagine the general public ever adopting an OS
 with a name that, if they google, has this, I don't know, weird connotation
 for a tech project.

 I mean, like, it's also something I wouldn't want to tell people I develop
 or have on a t-shirt because then when people google it they'd be like wtf.
 This guy is a real weirdo

 I don't really have any opinion on what the name should be, maybe a contest
 for choosing a new name could be held on the userlist or /r/rust as a way
 to build publicity for the project.
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160123/fd3df8a8/attachment-0001.html>

 From corey at octayn.net  Sun Jan 24 08:14:55 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 25 Jan 2016 00:14:55 +1100
 Subject: [robigalia-dev] Question on formal verification and whether
 there are plans to change the name
 In-Reply-To: <CADrbce1v=Fts7tC_qx7ccWXLtyQoFxeeN170wgd_9Kx+nt0eOg@mail.gmail.com>
 References: <CADrbce1v=Fts7tC_qx7ccWXLtyQoFxeeN170wgd_9Kx+nt0eOg@mail.gmail.com>
 Message-ID: <[email protected]>

 On Sat, Jan 23, 2016 at 04:23:27PM -0500, Kyle Marsh wrote:
 > 1. Are there plans to design / segment Robigalia around the ability to
 > ultimately formally verify (at least to a limited extent) additional system
 > components beyond the microkernel? Or is that more of a "nice to have if
 > it's possible later/non-goal of project" kind of thing
 >

 Yes, this is a large factor in my current thinkings. However, I suspect it
 will take at least 5-6 person months of effort to build a verification
 framework for sequential Rust, let alone concurrent Rust. And assumptions
 about invariants guaranteed by the type system cannot be used, since there's
 no formal proof that the type system is sound. The ability to reason about
 Rust code *at all*, in any proof system, will be a significant undertaking. In
 the short-to-medium term, integrating Rust with CAmkES will be the easiest way
 to get formal guarantees about systems built with Rust. The efforts by the
 RustBelt team will be useful, but results are likely years out. (And also
 in Coq, so an end-to-end proof in some HOL prover would be challenging.)

 I'm currently a "visiting student" at NICTA on the verification team. I'm
 hoping to use the knowledge I learn there to build said verification framework
 for Rust after I leave, potentially as my undergraduate thesis project.

 > 2. The name Robigalia - I'll be honest, it's basically right now why I'm
 > not interested in contributing. A project whose name seems to mean "dog
 > sacrifice" as it's hard to imagine the general public ever adopting an OS
 > with a name that, if they google, has this, I don't know, weird connotation
 > for a tech project.
 >

 That is one of the rites that took place during the festival. I'm somewhat
 open to changing the name of the overall project, but not the name of the
 POSIX component (Robigo), or the lower-level runtime (Phoma). It's all a huge
 pun on wheat rusts. The festival (Robigalia) was celebrated to appease Robigo,
 the goddess of crop disease.

 I've already dumped money on the domain name, though, and it's in all the
 licenses/license headers, as well as the DCO, and the name already has
 recognition in the Rust and seL4 communities. Plus the IRC channel, mailing
 list archives... it'd be an obnoxious migration.

 If the project ever gains popularity, it will be the first or second google
 result and have its own wikipedia article.

 > I mean, like, it's also something I wouldn't want to tell people I develop
 > or have on a t-shirt because then when people google it they'd be like wtf.
 > This guy is a real weirdo
 >

 Seems like someone should edit the wikipedia page to move the mention of that
 particular rite away from the second sentence ;) Really, I'm astonished anyone
 has brought this concern up. Animal (and human) sacrifice is part of our
 heritage, and the mentioned festival is so old by now. Like I said, I'm not
 opposed to changing it, and I don't want to trivialize your concern, but...

 > I don't really have any opinion on what the name should be, maybe a contest
 > for choosing a new name could be held on the userlist or /r/rust as a way
 > to build publicity for the project.
 >

 If we do rename it, it has to be *at least* as punny. It took us a few days to
 come up with these names!

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160125/b3ce8f0c/attachment.asc>

 From corey at octayn.net  Sun Jan 24 08:16:51 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Mon, 25 Jan 2016 00:16:51 +1100
 Subject: [robigalia-dev] My current status
 Message-ID: <[email protected]>

 Hi all,

 For those of you who I haven't talked to directly, my work on robigalia is
 currently on pause until I iron out some IP "issues" with NICTA.

 --
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160125/5f0a6249/attachment.asc>
 From corey at octayn.net  Tue Mar  1 12:42:36 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 2 Mar 2016 04:42:36 +1100
 Subject: [robigalia-dev] ARM support
 Message-ID: <[email protected]>

 Hi all,

 Been a while since I've sent an update. I just published version 0.0.20 of
 sel4-sys and sel4-start, as well as updated sel4-targets. This contains
 initial ARM support. It's untested right now, but builds succesfully, and the
 asm looks about right.

 I also created an initial acpica-sys crate:

    <https://gitlab.com/robigalia/acpica-sys>

 which is the first step towards <https://gitlab.com/robigalia/meta/issues/5>.

 I've also started on the sel4-alloc crate, for resource management, and
 sel4-vspace, for virtual memory layout management. After I'm done that, it's
 back to the virtio drivers.

 Someone in the libpnet community (faern) has started work on a TCP/IP stack
 built on libpnet, which is what I intend to use for Robigalia's network stack.
 If you're interested in helping out on that, pop into #libpnet on freenode.
 That work isn't specific to Robigalia, but benefits us enormously.

 -- 
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160302/5c06311e/attachment.asc>

 From corey at octayn.net  Sat Mar 12 14:21:46 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sun, 13 Mar 2016 06:21:46 +1100
 Subject: [robigalia-dev] ARM docs, cspace overhaul, allocators incoming!
 Message-ID: <[email protected]>

 Hi all,

 As can be seen on https://doc.robigalia.org/, documenation for both ARM and
 x86 is generated now. This also implies that all crates *build* for ARM as
 well!  Moving forward, hopefully most crates will have ARM and x86 support at
 roughly the same pace. The reality is that my time is limited, and x86 is my
 primary testing platform for now, and doing ARM will cut the speed at which
 platform functionality comes out in half. Maybe someone will step up to be the
 steward of ARM? ;)

 I've done a fairly big overhaul of sel4::cspace, and thus deployed new a new
 version, 0.0.2, of sel4. This came from work on the cspace allocators. There's
 a fair amount of documentation with it, that may or may not clarify some of
 the finer points of cspace handling.

 Speaking of allocators, I've made good progress on them yesterday, and should
 be finished with them today.

 I also made a simple checklist for the initial public announcement of phoma,
 https://gitlab.com/robigalia/meta/issues/10. However, there's not nearly
 enough information for some to be actionable without asking me what each item
 is about. But, some of the drivers are very simple (clock, timers, serial) or
 are very generic (cpio crate).

 Until next time,
 -- 
 cmr
 +610481762084
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160313/0c2f32fe/attachment.asc>

 From ernst at rohlicek.at  Thu Mar 31 16:08:24 2016
 From: ernst at rohlicek.at (Ernst Rohlicek)
 Date: Thu, 31 Mar 2016 22:08:24 +0200
 Subject: [robigalia-dev] Suggestion: add news page / blog
 Message-ID: <[email protected]>

 Greetings, I find the idea of seL4 + Rust + Linux compatibility
 intriguing and would like to follow your project.

 Please add a news page, or better, a small blog - with Atom/RSS rews
 feed for publishing activity.

 Maybe the Redox OS page at http://www.redox-os.org/ might be used for
 orientation.


 All the best,
 Ernst

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 884 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160331/1c342ba6/attachment.asc>

 From corey at octayn.net  Tue Mar  1 12:42:36 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 2 Mar 2016 04:42:36 +1100
 Subject: [robigalia-dev] ARM support
 Message-ID: <[email protected]>

 Hi all,

 Been a while since I've sent an update. I just published version 0.0.20 of
 sel4-sys and sel4-start, as well as updated sel4-targets. This contains
 initial ARM support. It's untested right now, but builds succesfully, and the
 asm looks about right.

 I also created an initial acpica-sys crate:

    <https://gitlab.com/robigalia/acpica-sys>

 which is the first step towards <https://gitlab.com/robigalia/meta/issues/5>.

 I've also started on the sel4-alloc crate, for resource management, and
 sel4-vspace, for virtual memory layout management. After I'm done that, it's
 back to the virtio drivers.

 Someone in the libpnet community (faern) has started work on a TCP/IP stack
 built on libpnet, which is what I intend to use for Robigalia's network stack.
 If you're interested in helping out on that, pop into #libpnet on freenode.
 That work isn't specific to Robigalia, but benefits us enormously.

 -- 
 cmr
 +16032392210
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160302/5c06311e/attachment.asc>

 From corey at octayn.net  Sat Mar 12 14:21:46 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Sun, 13 Mar 2016 06:21:46 +1100
 Subject: [robigalia-dev] ARM docs, cspace overhaul, allocators incoming!
 Message-ID: <[email protected]>

 Hi all,

 As can be seen on https://doc.robigalia.org/, documenation for both ARM and
 x86 is generated now. This also implies that all crates *build* for ARM as
 well!  Moving forward, hopefully most crates will have ARM and x86 support at
 roughly the same pace. The reality is that my time is limited, and x86 is my
 primary testing platform for now, and doing ARM will cut the speed at which
 platform functionality comes out in half. Maybe someone will step up to be the
 steward of ARM? ;)

 I've done a fairly big overhaul of sel4::cspace, and thus deployed new a new
 version, 0.0.2, of sel4. This came from work on the cspace allocators. There's
 a fair amount of documentation with it, that may or may not clarify some of
 the finer points of cspace handling.

 Speaking of allocators, I've made good progress on them yesterday, and should
 be finished with them today.

 I also made a simple checklist for the initial public announcement of phoma,
 https://gitlab.com/robigalia/meta/issues/10. However, there's not nearly
 enough information for some to be actionable without asking me what each item
 is about. But, some of the drivers are very simple (clock, timers, serial) or
 are very generic (cpio crate).

 Until next time,
 -- 
 cmr
 +610481762084
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160313/0c2f32fe/attachment.asc>

 From ernst at rohlicek.at  Thu Mar 31 16:08:24 2016
 From: ernst at rohlicek.at (Ernst Rohlicek)
 Date: Thu, 31 Mar 2016 22:08:24 +0200
 Subject: [robigalia-dev] Suggestion: add news page / blog
 Message-ID: <[email protected]>

 Greetings, I find the idea of seL4 + Rust + Linux compatibility
 intriguing and would like to follow your project.

 Please add a news page, or better, a small blog - with Atom/RSS rews
 feed for publishing activity.

 Maybe the Redox OS page at http://www.redox-os.org/ might be used for
 orientation.


 All the best,
 Ernst

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 884 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160331/1c342ba6/attachment.asc>
 From corey at octayn.net  Tue May  3 09:27:30 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 3 May 2016 23:27:30 +1000
 Subject: [robigalia-dev] Status Update
 Message-ID: <[email protected]>

 Hi all,

 If you missed it, I gave a talk about Rust + seL4 at the Rust Bay Area meetup
 last week:

 https://air.mozilla.org/bay-area-rust-meetup-april-2016/

 I'm currently doing a major sprint to publish a Robigalia paper in APSys 2016.
 There's a milestone on the issue tracker:

 https://gitlab.com/robigalia/meta/milestones/1

 By the end of the month, it should support a big enough chunk of Linux to play
 around in a shell and maybe run some interesting programs like Rogue. It's my
 only focus right now, besides maintaining my body ;)

 There will be a lot happening in a very short time! I'll send out an update at
 the end of the sprint. If you've got some time, there's plenty of
 low-intensity but important work that needs doing (especially fleshing out
 some of the structures needed for the system call ABI). Hop into IRC and I can
 give you some pointers.

 -- 
 cmr
 +610481782084
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160503/621c5ca5/attachment.asc>

 From nick at conky.org  Thu May  5 01:17:44 2016
 From: nick at conky.org (Nick Twyman)
 Date: Wed, 4 May 2016 22:17:44 -0700
 Subject: [robigalia-dev] Is the source for the website available?
 Message-ID: <CAH1Cxfq9g4qEmtqnX4Xs37w+bdnL1f8z0Hku4LABHf-2DZYFFw@mail.gmail.com>

 I am working through setting up a build environment on
 https://robigalia.org/build-environment.html and am finding some typos,
 etc. Is the source of the site in source control anywhere?

 If so, I'd be happy to make corrections and send pull requests. If not,
 what's the best way of sending you corrections,

 Cheers

 Nick
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160504/0b5c5ac8/attachment.html>

 From corey at octayn.net  Tue May  3 09:27:30 2016
 From: corey at octayn.net (Corey Richardson)
 Date: Tue, 3 May 2016 23:27:30 +1000
 Subject: [robigalia-dev] Status Update
 Message-ID: <[email protected]>

 Hi all,

 If you missed it, I gave a talk about Rust + seL4 at the Rust Bay Area meetup
 last week:

 https://air.mozilla.org/bay-area-rust-meetup-april-2016/

 I'm currently doing a major sprint to publish a Robigalia paper in APSys 2016.
 There's a milestone on the issue tracker:

 https://gitlab.com/robigalia/meta/milestones/1

 By the end of the month, it should support a big enough chunk of Linux to play
 around in a shell and maybe run some interesting programs like Rogue. It's my
 only focus right now, besides maintaining my body ;)

 There will be a lot happening in a very short time! I'll send out an update at
 the end of the sprint. If you've got some time, there's plenty of
 low-intensity but important work that needs doing (especially fleshing out
 some of the structures needed for the system call ABI). Hop into IRC and I can
 give you some pointers.

 -- 
 cmr
 +610481782084
 http://octayn.net/
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 473 bytes
 Desc: not available
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160503/621c5ca5/attachment.asc>

 From nick at conky.org  Thu May  5 01:17:44 2016
 From: nick at conky.org (Nick Twyman)
 Date: Wed, 4 May 2016 22:17:44 -0700
 Subject: [robigalia-dev] Is the source for the website available?
 Message-ID: <CAH1Cxfq9g4qEmtqnX4Xs37w+bdnL1f8z0Hku4LABHf-2DZYFFw@mail.gmail.com>

 I am working through setting up a build environment on
 https://robigalia.org/build-environment.html and am finding some typos,
 etc. Is the source of the site in source control anywhere?

 If so, I'd be happy to make corrections and send pull requests. If not,
 what's the best way of sending you corrections,

 Cheers

 Nick
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20160504/0b5c5ac8/attachment-0001.html>
 From corey at octayn.net  Wed Jan  4 12:52:10 2017
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 4 Jan 2017 12:52:10 -0500
 Subject: [robigalia-dev] Dropping gnueabi support, only gnueabihf?
 Message-ID: <[email protected]>

 Does anyone have opinions on this? It's yet another thing we need to
 test and maintain, and I don't even have a board that doesn't have hard
 float. Does anyone have a potential usecase that cares?

 -- 
 cmr
 http://octayn.net/
 +16038524272

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 488 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20170104/30e2f163/attachment.asc>

 From corey at octayn.net  Wed Jan  4 21:09:01 2017
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 4 Jan 2017 21:09:01 -0500
 Subject: [robigalia-dev] Dropping support for 32-bit x86?
 Message-ID: <[email protected]>

 I don't want to maintain this code, and I don't think it's valuable. The
 rt kernel really needs minimum of Ivy Bridge anyway, for the deadline
 timer, and if you have a processor supporting 64-bit, not much point in
 running a 32-bit OS.

 -- 
 cmr
 http://octayn.net/
 +16038524272

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 488 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20170104/8af7f917/attachment.asc>

 From corey at octayn.net  Wed Jan  4 12:52:10 2017
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 4 Jan 2017 12:52:10 -0500
 Subject: [robigalia-dev] Dropping gnueabi support, only gnueabihf?
 Message-ID: <[email protected]>

 Does anyone have opinions on this? It's yet another thing we need to
 test and maintain, and I don't even have a board that doesn't have hard
 float. Does anyone have a potential usecase that cares?

 -- 
 cmr
 http://octayn.net/
 +16038524272

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 488 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20170104/30e2f163/attachment.asc>

 From corey at octayn.net  Wed Jan  4 21:09:01 2017
 From: corey at octayn.net (Corey Richardson)
 Date: Wed, 4 Jan 2017 21:09:01 -0500
 Subject: [robigalia-dev] Dropping support for 32-bit x86?
 Message-ID: <[email protected]>

 I don't want to maintain this code, and I don't think it's valuable. The
 rt kernel really needs minimum of Ivy Bridge anyway, for the deadline
 timer, and if you have a processor supporting 64-bit, not much point in
 running a 32-bit OS.

 -- 
 cmr
 http://octayn.net/
 +16038524272

 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 488 bytes
 Desc: OpenPGP digital signature
 URL: <http://lists.robigalia.org/pipermail/robigalia-dev_lists.robigalia.org/attachments/20170104/8af7f917/attachment.asc>