Re: What would a modern LispOS look like?
- From: Robert Strandh <strandh@xxxxxxxx>
- Date: 28 Jun 2006 21:36:06 +0200
"bradb" <brad.beveridge@xxxxxxxxx> writes:
- How would seperation of privileges work? Multiple users/super user?
As Pascal Bourguignon said, EROS-like capabilities might be possible.
- What will the filesystem look like?
Again, as Pascal said, there need not be a file system. There also
need not be any protocol for persistence provided that EROS-like
universal persistence is used. Everything would just be persistent by
default.
Actually, persistence might turn out to be a much easier problem than
I had initially thought. Just make sure you have a battery, and make
sure you save all memory to disk before shutdown.
- How would support for other languages be?
One possibility would be to allow for programs written in unsafe
languages like C, to call such programs as Lisp functions, and to
remap the address space only then.
--
Robert Strandh
---------------------------------------------------------------------
Greenspun's Tenth Rule of Programming: any sufficiently complicated C
or Fortran program contains an ad hoc informally-specified bug-ridden
slow implementation of half of Common Lisp.
---------------------------------------------------------------------
.
- References:
- What would a modern LispOS look like?
- From: bradb
- What would a modern LispOS look like?
- Prev by Date: Re: Why is LISP syntax superior?
- Next by Date: Re: What would a modern LispOS look like?
- Previous by thread: Re: What would a modern LispOS look like?
- Next by thread: Re: What would a modern LispOS look like?
- Index(es):