<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.minix3.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.minix3.org/feed.php">
        <title>Wiki releases:3.2.0:developersguide</title>
        <description></description>
        <link>https://wiki.minix3.org/</link>
        <image rdf:resource="https://wiki.minix3.org/lib/tpl/minix3d/images/favicon.ico" />
       <dc:date>2026-04-30T19:07:35+0200</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:assemblylanguageprogramming&amp;rev=1415982669&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:blockprotocol&amp;rev=1415982904&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:bulkpkgsrc&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:codingstyle&amp;rev=1415983020&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:commitmessages&amp;rev=1415978571&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:contributions&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:cpureferencemanuals&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:datalinkprotocol&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:datastore&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:directorystructure&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:driverprogramming&amp;rev=1415978123&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:eclipsetutorial&amp;rev=1416313265&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:frompowerontologinprompt&amp;rev=1415978994&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:gcov&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:gitmigration&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:how-to-build-a-cross-compiler&amp;rev=1416222206&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:kernelapi&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:learningassemblyinminix&amp;rev=1415983264&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:makingpackmanpackage&amp;rev=1416222148&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:minixapi&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:newbuildsystem&amp;rev=1415985319&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:newkernelcall&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:obsoletetools&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:performancemeasurement&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pfsvfsprotocol&amp;rev=1415978213&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pipefs&amp;rev=1415978797&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pkgsrcupstreaming&amp;rev=1415985020&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:portingguide&amp;rev=1415984471&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:portingnetbsduserland&amp;rev=1415982517&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:posixandminix&amp;rev=1415984348&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:programmingminix&amp;rev=1416222296&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:rebuildingsystem&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:sef&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:serialout&amp;rev=1415984213&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:start&amp;rev=1415978528&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:statisticalprofiling&amp;rev=1415984561&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:syncpkgsrc&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:testingpkgsrc&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:testsuite&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:trackingcurrent&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usefultools&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:userspace-scheduling&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:userspace_scheduling&amp;rev=1415978852&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usinggit&amp;rev=1415983709&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usingnetbsdcode&amp;rev=1415983826&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vfsfsprotocol&amp;rev=1416222347&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vfsfsprotocolv2&amp;rev=1416222263&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vminternals&amp;rev=1415978908&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:volunteerpkgsrc&amp;rev=1415713928&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vtreefs&amp;rev=1425910552&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.minix3.org/lib/tpl/minix3d/images/favicon.ico">
        <title>Wiki</title>
        <link>https://wiki.minix3.org/</link>
        <url>https://wiki.minix3.org/lib/tpl/minix3d/images/favicon.ico</url>
    </image>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:assemblylanguageprogramming&amp;rev=1415982669&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:31:09+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:assemblylanguageprogramming</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:assemblylanguageprogramming&amp;rev=1415982669&amp;do=diff</link>
        <description>Assembly Language Programming

Assembly can be a frightening experience, even for well-seasoned C coders.  These resources are here to be of use to anyone wanting to work with assembly in Minix.

Learning Assembly Language

Main Page: Learning Assembly in MINIX

These are resources to aid users in learning assembler as it relates to Minix.  Note: the prerequisite for this is knowing C.  If you do not already know C, you'll save yourself many headaches by doing this first.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:blockprotocol&amp;rev=1415982904&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:35:04+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:blockprotocol</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:blockprotocol&amp;rev=1415982904&amp;do=diff</link>
        <description>The Block Device protocol

This page provides the official documentation of the block device driver protocol of MINIX 3. It describes the protocol used between VFS and file system servers on one side, and block drivers on the other. The current version documents the protocol used in git commit</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:bulkpkgsrc&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:bulkpkgsrc</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:bulkpkgsrc&amp;rev=1415713928&amp;do=diff</link>
        <description>Minix and Pkgsrc

pkgsrc has an advanced system to build each package in isolation of the world except for its stated dependencies. This is a good thing and helps package maintenance tremendously. It makes bulk building a little harder. In keeping with its philosophy, the new style (pbulk style building) requires bootstrapping a new pkgsrc instance (i.e. new prefix that is normally /usr/pkg), e.g. /usr/pbulk. The bulk build process needs to work in /usr/pkg, but that's where your currently insta…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:codingstyle&amp;rev=1415983020&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:37:00+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:codingstyle</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:codingstyle&amp;rev=1415983020&amp;do=diff</link>
        <description>Coding Style

Minix is standardizing on the netbsd coding style (based on KNF (Kernel Normal Form)) for new code. Mostly because the NetBSD import trend makes this the logical choice for a standard.

The canonical reference is in the git tree, also available as  /usr/share/misc/style in your MINIX machine, and</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:commitmessages&amp;rev=1415978571&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:22:51+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:commitmessages</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:commitmessages&amp;rev=1415978571&amp;do=diff</link>
        <description>Formatting of Commit Messages

	*  Please wrap your commits at 72 characters. You may use fmt(1) to do this for you.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:contributions&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:contributions</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:contributions&amp;rev=1415713928&amp;do=diff</link>
        <description>Contributions

This page keeps track of new patches.

/!\ This is probably temporary.

From the Mailing List

Please link to posts about patches below. Accepted ones can be deleted.
 Where &amp; What  release.sh configuration and options makeover  Dialog package and graphic installer using dialog  patch to solve server/apfs/buffer.c put_block function  patch for tildes in Spanish keymap, also asked for in Spanish keymap  Question regarding VM</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:cpureferencemanuals&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:cpureferencemanuals</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:cpureferencemanuals&amp;rev=1415713928&amp;do=diff</link>
        <description>CPU Manuals

INTEL Manuals

The Intel Corporation provides many useful documents on the

Pentium 4 Processor Technical Documentation page. 

Especially useful for helping you to understand the machine dependent
code of MINIX 3 on an IBM-PC compatible machine will be the
Manuals
section.  As of October 2004 the following manuals are available as PDF files
(read with Adobe Acrobat or Ghostview):</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:datalinkprotocol&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:datalinkprotocol</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:datalinkprotocol&amp;rev=1415713928&amp;do=diff</link>
        <description>The Data Link protocol

This page provides the official documentation of the Data Link protocol of MINIX 3. It describes the protocol used between the inet server, and ethernet drivers that control network interface card (NIC) hardware. The current version documents the protocol used in SVN revisions</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:datastore&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:datastore</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:datastore&amp;rev=1415713928&amp;do=diff</link>
        <description>DataStore

Stale page

The contents of this page must be revised to reflect the current state of MINIX3.

The MINIX 3 DataStore (DS) server allows components to back up data and
retrieve it after a restart and allows them to exchange data indirectly. 
For each publish request, an entry is stored in DS.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:directorystructure&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:directorystructure</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:directorystructure&amp;rev=1415713928&amp;do=diff</link>
        <description>Directory Structure

See man hier (note that that the output of man hier is not 100% accurate).</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:driverprogramming&amp;rev=1415978123&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:15:23+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:driverprogramming</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:driverprogramming&amp;rev=1415978123&amp;do=diff</link>
        <description>Programming Device Drivers in Minix

Introduction

This tutorial helps you to get started with programming device drivers on Minix in C. A device driver is a computer program which interacts with real hardware components. For example, the computer which you use now to read this web page has a device driver for the display monitor. Another example is the disk driver, which reads and writes raw data from disk(s) in your computer. Clearly, computer systems would be useless without good device drive…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:eclipsetutorial&amp;rev=1416313265&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-18T13:21:05+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:eclipsetutorial</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:eclipsetutorial&amp;rev=1416313265&amp;do=diff</link>
        <description>Using Eclipse in MINIX3 with Remote Explorer

The current support of MINIX3 toward other GNU software is still in progress, therefore coding with an IDE on the MINIX3 system is not yet possible. However, most of the programmers would prefer having their favorite IDE as a working and programming environment. One solution to that problem is the Remote System Explorer available for Eclipse. The plug-in has a lot of options targeted on Linux, Windows, and Unix boxes, including process control and re…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:frompowerontologinprompt&amp;rev=1415978994&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:29:54+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:frompowerontologinprompt</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:frompowerontologinprompt&amp;rev=1415978994&amp;do=diff</link>
        <description>From power-on to the login prompt

Boot monitor

When the power is turned on, the typical PC will try to read the first sector from the BIOS's boot device, such as the first floppy disk or the first hard disk, into memory, and execute it. The code obtained from the hard disk (from the so-called master boot sector) immediately will replace itself by the code found in the first sector of the active partition. Thus, the PC now is executing the bootstrap code found in the first sector of</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:gcov&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:gcov</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:gcov&amp;rev=1415713928&amp;do=diff</link>
        <description>GCC GCOV support by Anton Kuijsten

This wiki page is based on what was originally in Anton's &lt;minix/gcov.h&gt;.

Introduction

Code coverage testing is offered by gcc through gcov. Special compiler
flags add execution counters to a binary, along with counter increment
operations around each basic block of code. This way, the counters indicate
how many times a line of code has run.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:gitmigration&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:gitmigration</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:gitmigration&amp;rev=1415713928&amp;do=diff</link>
        <description>Git Migration

This page contains notes on the git migration.

Gerrit

We would like to have Gerrit.

Gerrit is a code review system that is more efficient and powerful than our current one. I (Ben) have an experimental install on
my own server, which is bad (because external, not it-maintained, etc.) but I'm so eager to try to work with it that I did it anyway - it's not critical, we can keep working without it - and we can switch to an official install in the future.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:how-to-build-a-cross-compiler&amp;rev=1416222206&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-17T12:03:26+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:how-to-build-a-cross-compiler</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:how-to-build-a-cross-compiler&amp;rev=1416222206&amp;do=diff</link>
        <description>This page describes a previous effort at cross compilation using GNU make. The currently supported method uses BSD make and is described in Crosscompiling.

This is a short how-to describing how to compile gcc cross compiler for sparc64 target (based on my previous work on L4 for sun4v)</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:kernelapi&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:kernelapi</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:kernelapi&amp;rev=1415713928&amp;do=diff</link>
        <description>MINIX 3 Kernel API

Stale page

The contents of this page must be revised to reflect the current state of MINIX3.

2012-03-31 note: with sys_vumap, the first step has been made to start documenting API calls rather than the protocol.

In general, kernel calls allows system processes to request kernel services, for example to perform privileged operations. This document briefly discusses the organization of kernel calls in MINIX 3 and provides an overview of all kernel calls.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:learningassemblyinminix&amp;rev=1415983264&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:41:04+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:learningassemblyinminix</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:learningassemblyinminix&amp;rev=1415983264&amp;do=diff</link>
        <description>Learning Assembly Language

These are resources to aid users in learning assembler as it relates to Minix.  Note: the prerequisite for this is knowing C.  If you do not already know C, you'll save yourself many headaches by doing this first.

Use the compiler</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:makingpackmanpackage&amp;rev=1416222148&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-17T12:02:28+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:makingpackmanpackage</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:makingpackmanpackage&amp;rev=1416222148&amp;do=diff</link>
        <description>Making a Packman Package

/!\ Packman is obsolete, please contribute pkgsrc packages only (see Testing Pkgsrc)

Making a MINIX 3 Package

We actively encourage people to write and port software to MINIX 3. MINIX 3 packages have a standard format that is required by the easypack package-manager. Here are the easy rules. Please stick to them, as they will make it easier for us to process your software, and easier for other people to install it the first time with no glitches.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:minixapi&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:minixapi</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:minixapi&amp;rev=1415713928&amp;do=diff</link>
        <description>APIs

Stale page

The contents of this page must be revised to reflect the current state of MINIX3.

Introduction

MINIX 3 is highly modular. The system consists of components, some of which offer services to
other components, some of which use services offered by other components, and some of which do both.
A component offering services does so through its Application Programming Interface (</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:newbuildsystem&amp;rev=1415985319&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T18:15:19+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:newbuildsystem</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:newbuildsystem&amp;rev=1415985319&amp;do=diff</link>
        <description>The GNU Minix 3 build system for cross-compilation

The new build system is a remake of the previous one using GNU make (gmake) to allow compilation of minix on various system using various compilers. The goal is to make development as simple as possible.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:newkernelcall&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:newkernelcall</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:newkernelcall&amp;rev=1415713928&amp;do=diff</link>
        <description>Adding a new Kernel Call in MINIX

(Working Draft)

This tutorial helps you to add a new kernel call in MINIX. Let's say your new kernel call is called sample.

	*  Add the prototype of your kernel function do_sample() in the file: /usr/src/kernel/system.h</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:obsoletetools&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:obsoletetools</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:obsoletetools&amp;rev=1415713928&amp;do=diff</link>
        <description>Obsolete tools

In addition to a number of still useful tools, MINIX also comes
with several tools that were created to ease configuration 
and development on MINIX without being part of any standard and are therefore
unlikely to be known to people familiar with other POSIX systems. Such tools
are now obsolete, but you may encounter them, perhaps when browsing history.
This page describes these tools. For more in-depth information consult their man pages.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:performancemeasurement&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:performancemeasurement</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:performancemeasurement&amp;rev=1415713928&amp;do=diff</link>
        <description>Measuring Performance in Minix

This page documents some features in Minix for measuring where the system is spending its time. If you are interested in optimising the system, this is the first thing to do.

top

First question is: is the time i/o time or cpu time? A simple way to see whether the system is working as hard as it can is 'top.' Then look at the 'idle' time. Example:</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pfsvfsprotocol&amp;rev=1415978213&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:16:53+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:pfsvfsprotocol</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pfsvfsprotocol&amp;rev=1415978213&amp;do=diff</link>
        <description>The PFS-VFS protocol

This page provides the official documentation of the PFS-VFS protocol of MINIX 3. It describes the protocol used between the PFS server and the VFS server. The current version documents the protocol used in SVN revision 9568. If you update this document because of changes to MINIX 3, please mention the revision number of the change in the wiki comment.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pipefs&amp;rev=1415978797&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:26:37+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:pipefs</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pipefs&amp;rev=1415978797&amp;do=diff</link>
        <description>The Pipe File System

This page documents the minix Pipe File System (PipeFS) server. It uses a 'top down' approach, giving the big picture first and then drilling down into the details. This document is current as of revision 7819.

Overview

The PipeFS server implements</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pkgsrcupstreaming&amp;rev=1415985020&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T18:10:20+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:pkgsrcupstreaming</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:pkgsrcupstreaming&amp;rev=1415985020&amp;do=diff</link>
        <description>pkgsrc upstreaming

Overview

Minix uses pkgsrc as it's primary package manager. The master branch of Minix's pkgsrc.git repository contains a pristine copy of the official pkgsrc repository. The minix-master branch contains a copy of the master branch with the Minix specific changes applied. The goal is to get all of the Minix specific changes into the official upstream pkgsrc repository which is developed and maintained by the NetBSD project. However, there is some work to be done to get the c…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:portingguide&amp;rev=1415984471&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T18:01:11+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:portingguide</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:portingguide&amp;rev=1415984471&amp;do=diff</link>
        <description>Porting Guide

Porting Guide Introduction

Porting software to MINIX from Linux or FreeBSD is non-trivial in most cases, but not exactly rocket science either. A major part of the work often has to do with altering/extending makefiles or build scripts. Recoding major parts of a piece of software generally is required for only software that does some or all of its work in kernel space. You can help MINIX by porting packages!</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:portingnetbsduserland&amp;rev=1415982517&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:28:37+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:portingnetbsduserland</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:portingnetbsduserland&amp;rev=1415982517&amp;do=diff</link>
        <description>Porting NetBSD Userland to MINIX 3

Introduction

Porting of NetBSD userland to MINIX 3 started with libc, and since then many libraries and utilities have been added to the system. The goal is to remove the utilities in /usr/src/commands and replace them with NetBSD's, and port additional utilities at the same time. Similarly, libraries from NetBSD can replace the MINIX libraries in /usr/src/lib and additional libraries from NetBSD can be added. This page is intended to organize and coordinate …</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:posixandminix&amp;rev=1415984348&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:59:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:posixandminix</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:posixandminix&amp;rev=1415984348&amp;do=diff</link>
        <description>POSIX and MINIX 3

MINIX 3 is POSIX conformant. This document discusses what that means.

What is POSIX?

 
&quot;To make it possible to write programs that could run on any UNIX
system, IEEE developed a standard for UNIX, called POSIX, that most
versions of UNIX now support.  POSIX defines a minimal system call
interface that conformant UNIX systems must support.  In fact, some
other operating systems now also support the POSIX interface.&quot;
    -- Operating Systems Design and Implementation, 2nd ed.,…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:programmingminix&amp;rev=1416222296&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-17T12:04:56+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:programmingminix</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:programmingminix&amp;rev=1416222296&amp;do=diff</link>
        <description>Programming in MINIX 3

This document covers some of the technical issues about using MINIX 3 and writing
code for it.

How can I learn to program in C?

The first edition of Andy Tanenbaum's 'Operating Systems Design
and Implementation included an Introduction to C</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:rebuildingsystem&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:rebuildingsystem</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:rebuildingsystem&amp;rev=1415713928&amp;do=diff</link>
        <description>Rebuilding the System

Rebuilding World

The easiest way is to rebuild “world”. It will rebuild and install the operating system, as well as all the utilities.


$ su
# cd /usr/src
# make world


That will create the necessary .depend files and library Makefiles; and then, proceed to install the new includes, build and install the new libraries; and then, rebuild the system (servers, drivers, and kernel), install it as a new image, and build and install the commands, with the new libraries.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:sef&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:sef</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:sef&amp;rev=1415713928&amp;do=diff</link>
        <description>The System Event Framework (SEF)

Stale page

The contents of this page must be revised to reflect the current state of MINIX3.

Introduction

This is a stub for the System Event Framework (SEF), a component of the system library that deals with system events in a centralized and convenient way.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:serialout&amp;rev=1415984213&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:56:53+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:serialout</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:serialout&amp;rev=1415984213&amp;do=diff</link>
        <description>Introduction

It's sometimes useful to add debugging prints to servers or drivers and have the output not show up on your screen, but redirected to serial. This way, you can log the prints to a text file or terminal on another box.

Enable serial on your Minix box</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:start&amp;rev=1415978528&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:22:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:start</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:start&amp;rev=1415978528&amp;do=diff</link>
        <description>MINIX 3 Developers Guide Table of Contents

The Developers Guide provides information on how to hack on MINIX 3. If you're new to MINIX 3 development, you should start here.

	*  Introduction
		*  Directory Structure


	*  Programming
		*  POSIX and MINIX 3
		*  Programming in MINIX 3
		*  X86 CPU Reference Manuals
		*  Useful tools specific to MINIX 3
		*  Device Driver Programming in MINIX 3
		*</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:statisticalprofiling&amp;rev=1415984561&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T18:02:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:statisticalprofiling</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:statisticalprofiling&amp;rev=1415984561&amp;do=diff</link>
        <description>Statistical profiling

Minix 3 supports statistical profiling. It is available in two versions. The basic one is based on BIOS RTC interrupts. This is available on any x86 machine and in virtual machines. As interrupts are not enabled in kernel this method does not make kernel profiling possible. The second method is using non-maskable interrupts (NMI) which also interrupt the kernel. This requires APIC mode. The NMIs are generated using performance counters. Each platform provides different cou…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:syncpkgsrc&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:syncpkgsrc</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:syncpkgsrc&amp;rev=1415713928&amp;do=diff</link>
        <description>Syncing the Minix pkgsrc Repository with Upstream

This is a guide intended for Minix developers. If you just want to install software on Minix and you ended up on this page, you might want to look at the Installing Binary Packages user guide.

Overview

Minix uses pkgsrc as it's primary package manager, and pkgsrc is generally distributed in source form via a version control system. Most people on non-Minix systems use CVS to checkout the latest copy from the NetBSD project. Since all of the Mi…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:testingpkgsrc&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:testingpkgsrc</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:testingpkgsrc&amp;rev=1415713928&amp;do=diff</link>
        <description>Testing pkgsrc on Minix

About this page

This page describes how to build packages with pkgsrc. It is intended for people who would like to help port packages and develop pkgsrc further. If you just want to install binary packages, you should read Installing Binary Packages. While this page also describes basic usage, more information can be found at</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:testsuite&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:testsuite</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:testsuite&amp;rev=1415713928&amp;do=diff</link>
        <description>The MINIX 3 Test Suite

The MINIX 3 sources include a test suite in /usr/src/test. Primarily, it tests POSIX conformance. This page describes how to run the test suite.

Compile the test suite

To test MINIX 3, at the command prompt (#) type 


cd /usr/src/test
make</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:trackingcurrent&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:trackingcurrent</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:trackingcurrent&amp;rev=1415713928&amp;do=diff</link>
        <description>Tracking Current

What does it mean?

Public releases are done at certain milestones; but development is continuous. Currently, all MINIX 3 sources are kept in a Git repository. The state of all of the newest versions of the files in the master Git repository (called 'minix', branch 'master') is called 'current', after a BSD convention. You can update your own MINIX 3 installation with those sources; and get a 'current' system. Doing that regularly in the context of MINIX could be called 'tracki…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usefultools&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:usefultools</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usefultools&amp;rev=1415713928&amp;do=diff</link>
        <description>Useful tools

MINIX comes with several tools that were created to ease configuration 
and development on MINIX that are not part of any standard and are therefore
unlikely to be known to people familiar with other POSIX systems. This page
describes these tools. For more in-depth information consult their man pages.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:userspace-scheduling&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:userspace-scheduling</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:userspace-scheduling&amp;rev=1415713928&amp;do=diff</link>
        <description>Userspace scheduling

How does it work?

Scheduling in Minix is simple multi-priority round robin. Each runnable processes in a its priority queue and has a quantum assigned. The assigned quantum of each process is periodically decreased. Each process is associated with a scheduler, e.g. a process that is responsible for making scheduling decisions for such a process.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:userspace_scheduling&amp;rev=1415978852&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:27:32+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:userspace_scheduling</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:userspace_scheduling&amp;rev=1415978852&amp;do=diff</link>
        <description>Userspace scheduling

How does it work?

Scheduling in Minix is simple multi-priority round robin. Each runnable processes in a its priority queue and has a quantum assigned. The assigned quantum of each process is periodically decreased. Each process is associated with a scheduler, e.g. a process that is responsible for making scheduling decisions for such a process.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usinggit&amp;rev=1415983709&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:48:29+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:usinggit</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usinggit&amp;rev=1415983709&amp;do=diff</link>
        <description>This page will give you a quickstart guide to git and the MINIX 3 git workflow.

A general Git quickstart site: gitready.com.

Git Basics

Git is a distributed version control system. As such, you don't just checkout a specific revision of your project as in subversion. Instead, you make a clone of the entire repository, including all history. You can 'commit' changes locally to your repository, but will need to 'push' them if you want your changes into a remote repository or, in our case, the m…</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usingnetbsdcode&amp;rev=1415983826&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T17:50:26+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:usingnetbsdcode</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:usingnetbsdcode&amp;rev=1415983826&amp;do=diff</link>
        <description>NetBSD libc invocation

NetBSD libc is in the master branch and hooked into the make world/elf-libraries procedure.

In the latest version of the master branch, gcc and clang *always* use the netbsd headers and libraries, and no elf libraries of the minix libraries are generated any more, to simplify things.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vfsfsprotocol&amp;rev=1416222347&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-17T12:05:47+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:vfsfsprotocol</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vfsfsprotocol&amp;rev=1416222347&amp;do=diff</link>
        <description>The VFS-FS protocol

This page provides the official documentation of the VFS-FS protocol of MINIX 3. It describes the protocol used between the VFS server and file servers responsible for mounted file systems. The current version documents the protocol used in Git commit</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vfsfsprotocolv2&amp;rev=1416222263&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-17T12:04:23+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:vfsfsprotocolv2</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vfsfsprotocolv2&amp;rev=1416222263&amp;do=diff</link>
        <description>Stale page

All the changes listed on this page, except for the dynamic updates and failure resilience support, have been merged into the VFS-FS protocol. The VFS-FS protocol documentation has been updated accordingly. Further changes to the protocol are being documented on that page</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vminternals&amp;rev=1415978908&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-14T16:28:28+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:vminternals</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vminternals&amp;rev=1415978908&amp;do=diff</link>
        <description>VM design notes

General

In order to encapsulate VM functionality, PM is split in process management and memory management. The memory management task is called VM and implements the memory part of the fork, exec, exit, etc calls, by being called by PM when those calls are done, and talks to SYSTEM instead of PM mostly. This has made PM architecture independent.</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:volunteerpkgsrc&amp;rev=1415713928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-11T14:52:08+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:volunteerpkgsrc</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:volunteerpkgsrc&amp;rev=1415713928&amp;do=diff</link>
        <description>Volunteer Pkgsrc

About

A secondary pkgsrc repository has been created on GitHub to allow volunteers to contribute to pkgsrc directly. It is currently experimental as its relationship to the primary pkgsrc repository has yet to be determined.

Care to Contribute?</description>
    </item>
    <item rdf:about="https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vtreefs&amp;rev=1425910552&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-03-09T15:15:52+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releases:3.2.0:developersguide:vtreefs</title>
        <link>https://wiki.minix3.org/doku.php?id=releases:3.2.0:developersguide:vtreefs&amp;rev=1425910552&amp;do=diff</link>
        <description>VTreeFS

The VTreeFS library provides a common base that allows the rapid development of read-only, in-memory, hierarchical file systems. Originally designed to form the basis of both DevFS and ProcFS (still ongoing efforts), it is both flexible and easy to use. The library provides the following functionality:</description>
    </item>
</rdf:RDF>
