Re: [Chicken-users] a file system using Chicken

[Ivan Raikov]

  Ah, the infamous Askemos. I am aware of it, of course, and it is a
very impressive work. If I ever get to work on a similar project, I
will probably borrow many ideas from Askemos (if not use it
wholesale), but I am specifically interested in using advanced
programming language techniques (like PCC) which allow certain
guarantees about the program logic to be embedded in the type system
or through annotations. And I wasn't going to start entirely from
scratch -- as part of my master's degree project, I implemented a
special-purpose compiler based on Greg Morrissett's Typed Assembly
Language (TAL), and the whole thing turned out to be fairly general,
so I want to port it to Scheme at some point. The original TAL idea
revolves around generating type-safe assembly code, given a System F
program as input, but the type system can be extended to make other
types of guarantees. So basically, I want to have a solid
statically-typed programming language foundation before I work on a
fancy high-level filesystem. Thank you for the detailed overview of
Askemos, though.

  -Ivan


"Joerg F. Wittenberger" <address@hidden> writes:

>
> I did end up with something like
> http://softeyes.net/A04538159df3258ea68544531bea1c006 (white paper
>>From 2002, PDF), the implementations looks roughly like this:
>
> level 1: comparable to git (see "man git" section "the object data
> base"): content addressed objects.  Askemos has only two types "blob"
> and "place".  Blob, as in git is a static byte sequence, addresses by
> it's sha256 has.  Blobs as well as places are referenced from other
> places via links.  Everythink place linked from the well know place
> (where - by "accident" higher level will store your current X509
> private host key is referenced as blob) is kept during garbage
> collection (of places).