From: "Art Yerkes" <ayerkes@gmvnetwork.com>
To: <caml-list@inria.fr>
Cc: <ak@gmvnetwork.com>, <jyerkes@hevanet.com>,
<ksherinian@gmvnetwork.com>, <mugwumpj@enteract.net>
Subject: [Caml-list] OCaml in the kernel (again)
Date: Wed, 23 Jan 2002 11:32:31 -0000 [thread overview]
Message-ID: <200201231132.g0NBWVh11770@mail.genxnet.com> (raw)
I found the idea of ocaml code in the kernel intriguing enough to do
some digging. It turns out that ocamlopt can compile a viable kernel
if one hacks hard enough, and this allows the C parts of the kernel to
give ocaml code a shot at initialization, including allowing ocaml code
to register callbacks, etc that will be called when the kernel is
running. The following page describes what's there, which while not
perfectly complete is enough to work with reasonably. This may be a
nice opportunity to do a project like foxnet, but to get everything
except the ethernet physical-layer driver into a nicer language. One
might consider that code thus written would be less exploitable by a
malicious hacker than equivalent C code.
Here is the page with instructions + files.
http://64.81.145.152/~arty/caml.html
Art
--
#define ENOTSUP 48 /* Operation not supported */
#define ENOTKANSTOTO 49 /* Not in kansas anymore, Toto */
#define EBADE 50 /* Invalid exchange */
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2002-01-23 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 11:32 Art Yerkes [this message]
2002-01-23 12:19 [Caml-list] ocaml " art
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200201231132.g0NBWVh11770@mail.genxnet.com \
--to=ayerkes@gmvnetwork.com \
--cc=ak@gmvnetwork.com \
--cc=caml-list@inria.fr \
--cc=jyerkes@hevanet.com \
--cc=ksherinian@gmvnetwork.com \
--cc=mugwumpj@enteract.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox