From: art <arty@speakeasy.net>
To: caml-list@inria.fr
Subject: [Caml-list] ocaml in the kernel (again)
Date: Wed, 23 Jan 2002 06:19:29 -0600 [thread overview]
Message-ID: <3C4EAA51.FF12EC95@speakeasy.net> (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 you try hard
enough, and
this allows the C parts of the kernel to give caml 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.
http://64.81.145.152/~arty/caml.html
Art
-------------------
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-24 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 12:19 art [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 11:32 [Caml-list] OCaml " Art Yerkes
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=3C4EAA51.FF12EC95@speakeasy.net \
--to=arty@speakeasy.net \
--cc=caml-list@inria.fr \
/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