<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.os.hurd.l4">
    <title>gmane.os.hurd.l4</title>
    <link>http://blog.gmane.org/gmane.os.hurd.l4</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6019"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6018"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6017"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6013"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6012"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6011"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6009"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6007"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/6004"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5988"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5987"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5983"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5981"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5973"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5966"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5965"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5964"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5962"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5910"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.os.hurd.l4/5909"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6019">
    <title>FOSDEM 2012 - Multiserver, microkernel-based operating systems devroom</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6019</link>
    <description>&lt;pre&gt;FOSDEM 2012 - Multiserver, microkernel-based operating systems devroom
*CALL FOR PARTICIPATION*
http://fosdem.org/2012

(apologies for cross-posting)

The developers of several free and open-source multiserver and/or
microkernel-based operating systems will meet at FOSDEM 2012 in
Brussels, Belgium and will share a developer room.

The devroom is currently looking for content in the form of talks
related to the area of multiserver and/or microkernel-based operating
systems. Possible topics include, but are not limited to:

  OS introduction to developers of other OS
  Subsystems and architecture
  Hardware and device drivers
  Tools and languages
  Release engineering and testing
  Experience and learning from mistakes
  Technical challenges
  Community and life with an OS-project
  Academia and education

Please send your talk proposal(s) to:

  microkernel-devroom&amp;lt; at &amp;gt;lists.fosdem.org

no later than by 2011-12-31.

Make sure to include the following in your proposal:
- title of your talk (will be printed in the&lt;/pre&gt;</description>
    <dc:creator>Jakub Jermar</dc:creator>
    <dc:date>2011-11-22T22:29:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6018">
    <title>FOSDEM 2012 -- devroom dedicated to [multiserver] microkernels,or generic alt-OS</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6018</link>
    <description>&lt;pre&gt;Hi!

I was contacted by jermar on IRC, a developer of HelenOS, which is
another multiserver microkernel based OS, &amp;lt;http://www.helenos.org/&amp;gt;.

He and also some folks from the MINIX3 group were thinking whether to
propose a developer room for the upcoming FOSDEM 2012.  The idea is for
having a devroom dedicated to [multiserver] microkernels, or a generic
alt-OS room as a fallback.

The deadline for applications is in three days already.

Are we interested in this?  I said we generally are, but that I have no
idea how many of us will make it to FOSDEM next year.

Then, our group will need to find things to do in the devroom, provide a
portion of the content.  This can be (but is not limited to):
presentations, brainstorming, coding sessions.

Please answer quickly.  Are you interested in this?  Can you already
forsee whether you'll make it to FOSDEM next year, 4th/5th February 2012,
&amp;lt;http://fosdem.org/2012/&amp;gt;.


Grüße,
 Thomas
&lt;/pre&gt;</description>
    <dc:creator>Thomas Schwinge</dc:creator>
    <dc:date>2011-10-24T17:01:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6017">
    <title>[ANNOUNCE] NOVA Microhypervisor 0.4 prerelease</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6017</link>
    <description>&lt;pre&gt;Hi,

The NOVA project is happy to announce that there is a new prerelease of the
NOVA microhypervisor available for download at http://www.hypervisor.org/
under the terms of the GNU General Public License version 2.

NOVA is based on a modern microhypervisor written in C++ and assembler.
The current implementation runs on multi-core x86 machines that support ACPI,
under QEMU (including VM support), and as a microkernel in a virtual machine
on top of itself. 

NOVA makes use of hardware virtualization features such as Intel VT-x/VT-d
or AMD-V, and facilitates running unmodified guest operating systems in
virtual machines with near-native performance.

Among other things, the new prerelease improves the security of device- and
interrupt assignment by using capabilities for these operations. There is
also a new hypercall for interacting with the scheduler.

At the same time, we've released a new version of the NOVA Userland (NUL).
While there are few user-visible changes, a lot has changed under the hood.
We ha&lt;/pre&gt;</description>
    <dc:creator>Udo A. Steinberg</dc:creator>
    <dc:date>2011-07-28T18:04:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6013">
    <title>uint64_t OR l4_uint64_t</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6013</link>
    <description>&lt;pre&gt;Today I got the source again from

(git.savannah.gnu.org/hurd/viengoos.git )

 then switch to  viengoos-on-bare-metal

 Got the cross-compiler and so.

 

 As i'd trying to fix some of my problems i saw

 at the file i named bellow some mistake might occurred.

 

        /libviengoos/t-addr.c 

        line 67 &amp;gt;              l4_uint64_t used ,but doesn't declared!

                               even at &amp;lt;l4/type.h&amp;gt;

                               Does uint64_t mistyped as l4_uint64_t?

                              (uint64_t had declared at hurd/addr.h)

                               

-Naghizodeh

&lt;/pre&gt;</description>
    <dc:creator>Naghizodeh,T.A-H</dc:creator>
    <dc:date>2011-04-07T15:52:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6012">
    <title>Error - Building Time</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6012</link>
    <description>&lt;pre&gt;Opps, I forgot to send the original message to the mailing list. Here it
is:

Try using the instructions here:

http://www.gnu.org/software/hurd/microkernel/viengoos/building.html

Viengoos only builds on x86_64 IIRC. Following those instructions should
atomatically build the cross-compiler that you need. It worked for me,
on PPC Debian Squeeze.

-Andrew



&lt;/pre&gt;</description>
    <dc:creator>Andrew Engelbrecht</dc:creator>
    <dc:date>2011-04-06T23:01:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6011">
    <title>booting viengoos with GRUB2 v. 1.99~rc1</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6011</link>
    <description>&lt;pre&gt;Has anyone gotten viengoos to boot using GRUB2 v. 1.99~rc1? I get the
following errors in qemu when try to boot Viengoos:

error: invalid offset in section header.
error: you need to load the multiboot kernel first

Looking at the date of the patch recommended for GRUB at
http://www.gnu.org/software/hurd/microkernel/viengoos/building.html ,
I figured that v. 1.97 would be the closest tried and tested version
of GRUB and therefore might work with viengoos. Unfortunately, v1.97,
v1.97.1, v1.97.2 and v1.98 don't cross-compile on my PPC computer.
Here are the errors I get when compiling v1.97:

gcc -Iutil/i386/pc -I../util/i386/pc -I. -I./include -I../include
-Wall -W -DGRUB_LIBDIR=\"/home/sudoman/src/gnuhurd/failedgrub/7/build/../install/lib/`echo
grub/i386-pc | sed 's&amp;amp;^&amp;amp;i386-pc-linux-gnu-&amp;amp;'`\" -g -O2 -DGRUB_UTIL=1
-MD -c -o grub_setup-util_i386_pc_grub_setup.o
../util/i386/pc/grub-setup.c
../util/i386/pc/grub-setup.c:38: error: initializer element is not constant
../util/i386/pc/grub-setup.c:38: error: (near i&lt;/pre&gt;</description>
    <dc:creator>Andrew Engelbrecht</dc:creator>
    <dc:date>2011-04-06T22:43:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6009">
    <title>Error - Building Time</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6009</link>
    <description>&lt;pre&gt;Hi,there

as i following building instruction, faced some problems:

 

 

$ autoreconf -i

$ mkdir test build

$ cd test/

$ ../configure --enable-l4 --host=i686-pc-viengoos-gnu \

        --enable-tests

 

 

   //  this configuration successfully finished with two warning

  //   warning  -  Unrecognized Options  :   --enable-tests 

 

$make check

 

  //  first the compilations process got terminated ,

  //  compile process stopped since it couldn't find one header file

  //  at  ../../libviengoos/viengoos

  //  i temporary fix this problem but there are still some problems

  

  //  the  i found that in directory="test/libviengoos"

  //  at Makefiles , there has been used  variable $(INCLUDES) but never

  //  assigned value .

 

$cat &amp;lt;dir&amp;gt;/test/libviengoos/Makefile | egrep '^INCLUDES'

   //      but no result founded 

 

   //after i called '$make check' the process show this messages on

   // screen

 

    

 

make[2] : Leaving direcotry '&amp;lt;DIR&amp;gt;/test/libviengoos'

make check-TESTS 

make[&lt;/pre&gt;</description>
    <dc:creator>Naghizodeh,T.A-H</dc:creator>
    <dc:date>2011-04-06T17:54:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6007">
    <title>Some Mistakes  at StarUp</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6007</link>
    <description>&lt;pre&gt;Hi there,
I used qemu and Grub Legacy (floppy disk image) for running kernel with
it's modules 
I follow mostly from the instruction on README
when i try to boot on grub i saw this , it's seem the kernel going to
starting , but ,it doesn't .
system stop by give me this log file on the screen (i'd typed them) 
 
laden (ff0720ff):kip_fixup:54: Booting an x2 Kernel.
laden (ff0720ff):kip_fixup:70: Sigma0: Low 0x20000, Hight 0x29524, IP
0x20000, SP 0x0
laden (ff0720ff):kip_fixup:75: Root: Low 0x400000, Hight 0x4d40cc, IP
0x400000, SP 0x0
laden (ff0720ff):kip_fixup:93: Memory Map 1: Type shared(4)/0, Low 0x0,
Hight 0xfffffffffffffc00
laden (ff0720ff):kip_fixup:93: Memory Map 2: Type conventional(1)/0, Low
0x0, High 0x9f000
laden (ff0720ff):kip_fixup:93: Memory Map 3: Type arch(15)/2, Low
0x9f400, High 0x9fc00
laden (ff0720ff):kip_fixup:93: Memory Map 4: Type arch(15)/2, Low
0xf0000, High 0xffc00
laden (ff0720ff):kip_fixup:93: Memory Map 5: Type conventional(1)/0, Low
0x100000, High 0x7ffcc00
laden (ff0720ff):kip_f&lt;/pre&gt;</description>
    <dc:creator>Naghizodeh T.,A-H</dc:creator>
    <dc:date>2011-04-05T16:51:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/6004">
    <title>[ANNOUNCE] NOVA Microhypervisor 0.3 prerelease</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/6004</link>
    <description>&lt;pre&gt;Hi,

The NOVA project is happy to announce that there is a new prerelease of the
NOVA microhypervisor available for download at http://www.hypervisor.org/
or http://os.inf.tu-dresden.de/~us15/nova/ under the terms of the
GNU General Public License version 2.

NOVA is based on a modern microhypervisor written in C++ and assembler.
The current implementation runs on multi-core x86 machines that support ACPI,
under QEMU (including VM support), and as a microkernel in a virtual machine
on top of itself. 

NOVA makes use of hardware virtualization features such as Intel VT-x/VT-d
or AMD-V, and facilitates running unmodified guest operating systems in
virtual machines with near-native performance.

The new release brings virtual-machine support to QEMU and older AMD CPUs,
both of which lack nested paging. Furthermore, the microhypervisor can now
translate related capabilities during message passing.

Cheers,

- Udo
&lt;/pre&gt;</description>
    <dc:creator>Udo A. Steinberg</dc:creator>
    <dc:date>2011-02-16T21:55:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5988">
    <title>Viengoos still active?</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5988</link>
    <description>&lt;pre&gt;Hi,

 I'd like to know the status of the Viengoos project. Is it still active? Looking at git:

last changeMon, 19 Jan 2009 22:34:13 +0000

The last change was made almost a year.

The question is: Is there still a project for a new GNU microkernel aside GNU Mach? Is Viengoos it or are there new projects blooming?

Thank You


      


&lt;/pre&gt;</description>
    <dc:creator>Dok Sander</dc:creator>
    <dc:date>2010-12-04T03:54:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5987">
    <title>If help is needed</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5987</link>
    <description>&lt;pre&gt;Hi!

I would like to help in any way I can this project. To give you an 
overview of my skills I am a fairly good c,c++ programmer and I have 
some basic understanding Operating Systems and hardware architecture. 
Please let me know If I can help in any way.

Thank you!


&lt;/pre&gt;</description>
    <dc:creator>TDTwister Gmail</dc:creator>
    <dc:date>2010-08-10T20:57:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5983">
    <title>Scheduling of "foreground" applications</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5983</link>
    <description>&lt;pre&gt;Hi,

A while back in some discussion here the idea was mentioned to
automatically give "foreground" applications more priority.

Someone just brought up an old paper, which -- if I'm reading the
abstract right -- seems to be about doing precisely that:

   http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/evans.txt

-antrik-


&lt;/pre&gt;</description>
    <dc:creator>olafBuddenhagen&lt; at &gt;gmx.net</dc:creator>
    <dc:date>2010-06-16T19:00:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5981">
    <title>a bug of the slab implementation in viengoos?</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5981</link>
    <description>&lt;pre&gt;Hello,

I recently ported the slab implementation in viengoos to Hurd. It seems that the
refcount field of hurd_slab isn't initialized when it is created in grow(). here
is the patch to fix it.

Best regards,
Zheng Da
&lt;/pre&gt;</description>
    <dc:creator>Da Zheng</dc:creator>
    <dc:date>2010-05-31T13:26:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5973">
    <title>licensing</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5973</link>
    <description>&lt;pre&gt;Hello,
I am looking for the licenses/licensing or links to the licenseslicensing of
the Hurd, the Viengoos microkernel and the Coyotos microkernel.

Thanks,
Steve.
&lt;/pre&gt;</description>
    <dc:creator>steve paesani</dc:creator>
    <dc:date>2010-04-23T00:37:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5966">
    <title>Contributing to Hurd</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5966</link>
    <description>&lt;pre&gt;I want to contribute my programming skills to complete GNU system.
Since Hurd is the only part thats is incomplete in whole GNU system, I
want to work on it. I went to this page and found there are 3 ways to
contribute:

http://www.gnu.org/s/hurd/contributing.html

   1.  Documentation
   2. The System Itself
         1. Hurd on Mach
               1. Porting Packages
               2. Open Issues
         2. Hurd on a modern microkernel


I chose the "Hurd on modern microkernel"   as the path to walk on as I
am neither interesting in web-side nor in outdated Mach. Any
directions to start ?




&lt;/pre&gt;</description>
    <dc:creator>arnuld uttre</dc:creator>
    <dc:date>2010-04-20T10:13:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5965">
    <title>Codezero v0.3 is out</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5965</link>
    <description>&lt;pre&gt;Hello,

I would like to announce that Codezero v0.3 release is out and we have
added support for ARMv7 architecture and SMP Cortex-A9 cpus in this release.

The ARMv7 support has been tested on a Versatile Express Cortex A9
platform which contains four cores. Beagleboard support is also going to
be available soon - due to omap3 non-conformity to ARMv7 a few issues
left for fixing.

Finally, we have preliminary support for the Genode OS Framework from
Genode labs. We are improving on this and plan to show a demo of their
application stack in multi-core expo next month:

http://www.multicore-expo.com
http://esc-sv09.techinsightsevents.com/

I would be happy to demo the software to anyone attending.

Thank you,

&lt;/pre&gt;</description>
    <dc:creator>Bahadir Balban</dc:creator>
    <dc:date>2010-03-25T22:26:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5964">
    <title>FOSDEM</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5964</link>
    <description>&lt;pre&gt;Hello,

For those going to FOSDEM, I would like to invite you to a talk I'll be
giving about Iris, my new kernel.  It's currently targeted at the Ben
NanoNote, a very small handheld computer.  For that reason, the talk is
scheduled in the embedded devroom (Lameere).  It's on saturday at 18:00.

As you probably know, Olaf is also giving two talks, both on Sunday in
the alt-OS devroom (AW1.105).  Unfortunately, I will not be at the first
one, because it is at the same time as the talk about RepRap, which
sounds so extremely cool, I have to go there.

See you this weekend,
Bas
&lt;/pre&gt;</description>
    <dc:creator>Bas Wijnen</dc:creator>
    <dc:date>2010-02-01T14:52:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5962">
    <title>viengoos build errors</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5962</link>
    <description>&lt;pre&gt;
 

 Hi I'm trying to build viengoos but am getting an error, I have followed the documentation and successfuly built the cross compiler but when I run make again to actually build viengoos itself I get:

libtool: Version mismatch error.  This is libtool 2.2.4, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4
libtool: and run autoconf again.
make[4]: *** [alter.lo] Error 63
make[4]: Leaving directory `/home/chris200x9/viengoos/build/benchmarks/sqlite/build'
make[3]: *** [all-local] Error 2
make[3]: Leaving directory `/home/chris200x9/viengoos/build/benchmarks/sqlite'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/chris200x9/viengoos/build/benchmarks'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/chris200x9/viengoos/build'
make: *** [all] Error 2

Any help would be much appriciated.


&lt;/pre&gt;</description>
    <dc:creator>chris200x9&lt; at &gt;aol.com</dc:creator>
    <dc:date>2010-01-19T16:31:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5910">
    <title>Codezero v0.2 Capabilities</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5910</link>
    <description>&lt;pre&gt;Hi All,

I would like to share with you the current status of Codezero
development as we make the 0.2 release. I am looking into feedback on
various design issues, particularly on capabilities.

I think I have understood Hurd requirements to a good extent, and
Codezero has different final goals compared to the ideal kernel that
Hurd needs.

That said, Codezero has a lot of common grounds with Hurd kernel
requirements, and I would like to focus discussion on these common areas.

What I need is your opinion on our existing capability design, in any
aspect. Security, usability, applicability ... We have implemented
capabilities in Codezero to a good extent, and the design requires
feedback (details to follow on my next email).

What this will bring back to you is that you have the chance to see a
live kernel that has a capability implementation with resources reduced
to a useful small set (e.g. kernel resources), and one that is
attempting to apply it to real practice. You will see your feedback
being implement&lt;/pre&gt;</description>
    <dc:creator>Bahadir Balban</dc:creator>
    <dc:date>2009-12-07T12:59:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5909">
    <title>Codezero Microkernel v0.2 Released</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5909</link>
    <description>&lt;pre&gt;I would like to announce that Codezero Microkernel v0.2 has been released.

On this release, the microkernel is now fully capability checked, and we
introduced the notion of containers to provide isolated execution
environments. Please see below for a brief description.


1.) Containers

In Codezero containers provide the architectural infrastructure for
isolation of execution environments. Each container is allocated with a
set of address spaces, threads, and any other resource that would
otherwise be globally available on the platform, such as virtual and
physical memory.

Using the simple notion of containers, it is possible to build any type
of software design hierarchy. A hierarchical client/server design, or
multi-threaded standalone applications are both possible scenarios.


2.) Capabilities

Capabilities protect all resources maintained by the kernel. Currently,
all system calls are protected by capabilities, except a few trivial
ones that have been left out. Physical and virtual memory, typed memor&lt;/pre&gt;</description>
    <dc:creator>Bahadir Balban</dc:creator>
    <dc:date>2009-12-07T13:01:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.os.hurd.l4/5840">
    <title>Barrelfish: microkernel(?) + capabilities + distributedheterogeneous cores + formal proofs + Haskell</title>
    <link>http://comments.gmane.org/gmane.os.hurd.l4/5840</link>
    <description>&lt;pre&gt;Since no one else has mentioned it yet, let me present, The Barrelfish  
Operating System:

http://barrelfish.org/

As described in this paper:

http://barrelfish.org/barrelfish_sosp09.pdf

    "We investigate a new OS structure, the multikernel, that treats  
the machine as a
network of independent cores, assumes no inter-core sharing at the
lowest level, and moves traditional OS functionality to a distributed
system of processes that communicate via message-passing."

This paper describes the use of DSLs and DSL -&amp;gt; C compilers written in  
Haskell to generate low-level kernel code:

http://www.barrelfish.org/fof_plos09.pdf

The aim is to be able to build provably correct DSLs and compilers  
fast enough that you would actually prefer to use them as part of the  
development process instead of just doing the low-level C code by hand.

- jeremy



&lt;/pre&gt;</description>
    <dc:creator>Jeremy Shaw</dc:creator>
    <dc:date>2009-10-02T15:33:10</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.os.hurd.l4">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.os.hurd.l4</link>
  </textinput>
</rdf:RDF>

