Re: OS decisions

Ram Vedam <[email protected]> Sat, 13 Jun 2009 18:57:43 -0500
Newsgroups gmane.lisp.movitz.devel
Message-ID <[email protected]>
--===============0497230928==
Content-Type: multipart/alternative; boundary=002215046b6748976c046c4397cd

--002215046b6748976c046c4397cd
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Is Movitz or should Movitz be geared towards becoming a multiuser system? I
think it would be a good idea... and if that is the eventual goal, then
memory protection is a very good idea. Though wouldn't you need memory
protection for process isolation to work correctly? Unless I'm missing
something here...

Ram

On Sat, Jun 13, 2009 at 6:30 PM, Brian Makin <[email protected]> wrote:

>
> On Jun 13, 2009, at 5:35 PM, Shawn Betts wrote:
>
> > On Fri, Jun 12, 2009 at 5:40 PM, Brian Makin<[email protected]> wrote:
> >> Some architecture questions... some of which may not have been
> >> decided
> >> yet.
> >>
> >> Do we want to support 32 and 64 bit?
> >
> > I believe Frode was working on a 64bit port.
> >
> >> SMP?
> >
> > Sure, why not?
> >
> >> Will there be virtual memory?
> >
> > You sorta have to if you want to access all the computer's memory
> > don't you?
> >
>
> More of a question of paging.  You could decide that ram sizes are
> large enough that we don't need it...
>
> >> Memory protection?
> >
> > In many ways lisp doesn't need memory protection since you don't
> > create pointers out of thin air like in C. That said, it could be
> > useful for security purposes if movitz was a multiuser system.
> >
>
> Protection between user processes probably aren't as important.  In a
> multiuser system you would still want projection between user and
> kernel space however.
>
> >> What kind of file system? or use an existing one?
> >
> > I think an existing one would be fine.
> >
> >> Will it have a console or be gui driven?
> >
> > Both of course! :)
> >
> > -Shawn
> >
> > _______________________________________________
> > movitz-devel site list
> > [email protected]
> > http://common-lisp.net/mailman/listinfo/movitz-devel
>
>
> _______________________________________________
> movitz-devel site list
> [email protected]
> http://common-lisp.net/mailman/listinfo/movitz-devel
>

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

Is Movitz or should Movitz be geared towards becoming a multiuser system? I=
 think it would be a good idea... and if that is the eventual goal, then me=
mory protection is a very good idea. Though wouldn&#39;t you need memory pr=
otection for process isolation to work correctly? Unless I&#39;m missing so=
mething here...<br>
<br>Ram<br><br><div class=3D"gmail_quote">On Sat, Jun 13, 2009 at 6:30 PM, =
Brian Makin <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">meri=
[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex=
; padding-left: 1ex;">
<div class=3D"im"><br>
On Jun 13, 2009, at 5:35 PM, Shawn Betts wrote:<br>
<br>
&gt; On Fri, Jun 12, 2009 at 5:40 PM, Brian Makin&lt;<a href=3D"mailto:meri=
[email protected]">[email protected]</a>&gt; wrote:<br>
&gt;&gt; Some architecture questions... some of which may not have been<br>
&gt;&gt; decided<br>
&gt;&gt; yet.<br>
&gt;&gt;<br>
&gt;&gt; Do we want to support 32 and 64 bit?<br>
&gt;<br>
&gt; I believe Frode was working on a 64bit port.<br>
&gt;<br>
&gt;&gt; SMP?<br>
&gt;<br>
&gt; Sure, why not?<br>
&gt;<br>
&gt;&gt; Will there be virtual memory?<br>
&gt;<br>
&gt; You sorta have to if you want to access all the computer&#39;s memory<=
br>
&gt; don&#39;t you?<br>
&gt;<br>
<br>
</div>More of a question of paging. =A0You could decide that ram sizes are<=
br>
large enough that we don&#39;t need it...<br>
<div class=3D"im"><br>
&gt;&gt; Memory protection?<br>
&gt;<br>
&gt; In many ways lisp doesn&#39;t need memory protection since you don&#39=
;t<br>
&gt; create pointers out of thin air like in C. That said, it could be<br>
&gt; useful for security purposes if movitz was a multiuser system.<br>
&gt;<br>
<br>
</div>Protection between user processes probably aren&#39;t as important. =
=A0In a<br>
multiuser system you would still want projection between user and<br>
kernel space however.<br>
<div><div></div><div class=3D"h5"><br>
&gt;&gt; What kind of file system? or use an existing one?<br>
&gt;<br>
&gt; I think an existing one would be fine.<br>
&gt;<br>
&gt;&gt; Will it have a console or be gui driven?<br>
&gt;<br>
&gt; Both of course! :)<br>
&gt;<br>
&gt; -Shawn<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; movitz-devel site list<br>
&gt; <a href=3D"mailto:[email protected]">movitz-devel@common-li=
sp.net</a><br>
&gt; <a href=3D"http://common-lisp.net/mailman/listinfo/movitz-devel" targe=
t=3D"_blank">http://common-lisp.net/mailman/listinfo/movitz-devel</a><br>
<br>
<br>
_______________________________________________<br>
movitz-devel site list<br>
<a href=3D"mailto:[email protected]">[email protected]=
t</a><br>
<a href=3D"http://common-lisp.net/mailman/listinfo/movitz-devel" target=3D"=
_blank">http://common-lisp.net/mailman/listinfo/movitz-devel</a><br>
</div></div></blockquote></div><br>

--002215046b6748976c046c4397cd--


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