Re: compiling LiCE for Movitz

Ram Vedam <[email protected]> Sat, 21 Nov 2009 17:27:20 -0600
Newsgroups gmane.lisp.movitz.devel
Message-ID <[email protected]>
--===============2087182141==
Content-Type: multipart/alternative; boundary=0016e644c18e1642480478e9ef4e

--0016e644c18e1642480478e9ef4e
Content-Type: text/plain; charset=ISO-8859-1

I found the tmp directory with an ext2fs implementation. I'm just starting
to look at it.

Ram

On Sat, Nov 21, 2009 at 4:02 PM, Andreas Davour <[email protected]> wrote:

> On Sat, 21 Nov 2009, Ram Vedam wrote:
>
>  Have there been any attempts at writing a filesystem for Movitz? I think
>> that LiCE would definitely compile with no adjustment to Shawn's source if
>> there was a filesystem on Movitz, since it would mean that those macros /
>> functions associated with file I/O would have been implemented. In
>> retrospect, I guess I should have started with that first. I haven't seen
>> any references to an attempted filesystem inside the Movitz source, but I
>> may be looking in the wrong place.
>>
>
> There used to be a tmp directory with some stuff about ext3. I haven't
> checked out the source in a long time, since I dropped out of lisp for a
> while. My source is two computers (generations!) away...
>
> Filesystems was exactly what I was about to do for movitz, and other have
> also tried. It sure would be nice to have. I have so much to do these days,
> but if I could get the lisp bug again I think some basis could be laid quite
> easy.
>
>
> /andreas
>
> --
> A: Because it fouls the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
>

--0016e644c18e1642480478e9ef4e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I found the tmp directory with an ext2fs implementation. I&#39;m just start=
ing to look at it. <br><br>Ram<br><br><div class=3D"gmail_quote">On Sat, No=
v 21, 2009 at 4:02 PM, Andreas Davour <span dir=3D"ltr">&lt;<a href=3D"mail=
to:[email protected]">[email protected]</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class=3D"im"=
>On Sat, 21 Nov 2009, Ram Vedam wrote:<br>
<br>
</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"border-l=
eft: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:=
 1ex;">
Have there been any attempts at writing a filesystem for Movitz? I think<br=
>
that LiCE would definitely compile with no adjustment to Shawn&#39;s source=
 if<br>
there was a filesystem on Movitz, since it would mean that those macros /<b=
r>
functions associated with file I/O would have been implemented. In<br>
retrospect, I guess I should have started with that first. I haven&#39;t se=
en<br>
any references to an attempted filesystem inside the Movitz source, but I<b=
r>
may be looking in the wrong place.<br>
</blockquote>
<br></div>
There used to be a tmp directory with some stuff about ext3. I haven&#39;t =
checked out the source in a long time, since I dropped out of lisp for a wh=
ile. My source is two computers (generations!) away...<br>
<br>
Filesystems was exactly what I was about to do for movitz, and other have a=
lso tried. It sure would be nice to have. I have so much to do these days, =
but if I could get the lisp bug again I think some basis could be laid quit=
e easy.<div>
<div></div><div class=3D"h5"><br>
<br>
/andreas<br>
<br>
-- <br>
A: Because it fouls the order in which people normally read text.<br>
Q: Why is top-posting such a bad thing?<br>
A: Top-posting.<br>
Q: What is the most annoying thing on usenet and in e-mail?<br>
</div></div></blockquote></div><br>

--0016e644c18e1642480478e9ef4e--


--===============2087182141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline