From: Nala Ginrut <nalaginrut@gmail.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: l4-hurd@gnu.org, guile-user@gnu.org
Subject: Re: GNU Hurd on $scheme (was: [ANN] the Guile 100 Programs Project)
Date: Sat, 02 Feb 2013 11:51:43 +0800 [thread overview]
Message-ID: <1359777103.3021.72.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CAN3veRcQCVn_GRoZh_pDz4gO7mhcvcrhiuFWY7Qcq7k2x66t6g@mail.gmail.com>
On Sat, 2013-02-02 at 10:49 +0800, Daniel Hartwig wrote:
> [Hello l4-hurd, I see you have been quiet lately.]
>
> On 2 February 2013 01:28, Nala Ginrut <nalaginrut@gmail.com> wrote:
> > On Fri, 2013-02-01 at 16:40 +0000, Ian Price wrote:
> >> Heh, reimplementing coreutils in Scheme has been a plan of mine for a
> >> while, as part of justifying my Iteratees library, but that has taken a
> >> sideline to newer and shinier projects.
> >>
> >
> > Maybe another new project, say, rewrite GNU with Guile, include part of
> > HURD, heh? I even get the name, GoG, GNU on Guile. ;-P
> >
>
> Something I have thought about for some time. Next on the TODO list :-)
>
>
> There is a paper by Rees, _A Security Kernel Based on the
> Lambda-Calculus_. It discusses a Lisp dialect, Scheme¯, similar to
> Scheme but with certain operations removed; in there place are some
> logical guarantees with implications for security for any code written
> in the dialect. This is used to construct a security kernel, W7,
> which becomes the basis for Scheme48 (a language supporting R5RS).
>
> I don't want to get in to the details of the paper, I think that many
> on this list will be familiar with it. Suffice to say that the
> security kernel provides concepts that closely map to a capability
> model. Also, verified processes can run within the same machine
> process and I wonder if this has implications for the communication
> overhead that microkernel systems tend to get labelled with. In
> theory the security kernel, core services, and any Scheme (and other)
> language programs should be able to reside in the same process without
> having to implement access restrictions beyond those implicit in the
> language.
>
> After bootstrapping my current pet project, I intend to explore the
> ideas in this paper as they relate to the Hurd. As I am quite fond of
> Guile I plan to proceed roughly as follows:
> - port Scheme¯ to the Guile language stack;
> - get W7 or something similar running on this;
> - implement required Hurd interfaces;
> - port some of the current Hurd servers and userland to the Scheme in
> this stack;
> - …
> - profit!
>
> Maybe bypassing the first stages and use Scheme48 instead.
>
> I believe having some sort of system running in Scheme would be very
> useful for exploring design and architectural issues, regardless of
> whether it is a practical or fast performing implementation.
>
> Anyone interested in collaborating on such a project, or have comments
> regarding the paper and the implications for the Hurd? Nala, you
> sound interested, and we will certainly benefit from some of the
> userland being ported as part of the Guile 100 Programs Project.
>
Yes, I'm definitely interested on it. Several years ago, I decided to
become an OS hacker and I want to research OS design, but then I became
a language/compiler hacker after I read SICP, I don't know how it is...
Actually, I planed to implement MiG with Guile, but I delayed that since
I need to read many papers about Hurd which is worthy for the hack.
Now this kind of OS, I can't find a good entrance for it, maybe this GNU
Hurd on $scheme project is a good way to start.
Anyway, count me in! ;-P
> Regards
next prev parent reply other threads:[~2013-02-02 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 2:49 GNU Hurd on $scheme (was: [ANN] the Guile 100 Programs Project) Daniel Hartwig
2013-02-02 3:51 ` Nala Ginrut [this message]
2013-02-02 10:19 ` GNU Hurd on $scheme Ludovic Courtès
2013-02-02 16:36 ` Nala Ginrut
2013-02-02 16:44 ` Ludovic Courtès
2013-02-02 10:19 ` Ludovic Courtès
2013-02-03 0:04 ` Daniel Hartwig
2013-02-04 12:32 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1359777103.3021.72.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=l4-hurd@gnu.org \
--cc=mandyke@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).