<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
For documentation, one might want to take a look at the bitsavers.org
site, specifically...<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.bitsavers.org/pdf/dec/">http://www.bitsavers.org/pdf/dec/</a><br>
<br>
(it's also a good site for older software too)<br>
<blockquote cite="mid:754314.84487.qm@web34505.mail.mud.yahoo.com"
type="cite">
<style type="text/css"><!-- DIV {margin:0px;} --></style>
<div
style="font-family: times new roman,new york,times,serif; font-size: 10pt;">
<div>> I know; I only think that, in a first time, we have to
write a stable kernel on only _one_ arch. In a second time, we can add
some archs.<br>
<br>
That's the plan: a portable kernel (i.e. portable C, easy assembly
migration), written for x86 first then ported to whatever other
architecture we want/need later in the process. <br>
<br>
> If this is only a 64-bit interface, will it still be possible to
write something like VEST that would translate Vax and Alpha binaries
into x86 binaries?<br>
<br>
Never heard of it, but to tailor a precompiled VAX/Alpha VMS binary for
our kernel on x86 would require a lot more than that: think virtual
memory and instruction translation (JIT?) - I was under the impression
that the existing code could load and execute a precompiled VMS binary,
but I planned on doing this for our kernel anyways after we get it
running. Just don't expect a whole lot for the case of hardware
drivers, referring to an earlier discussion, but TCP/IP, filesystem and
other QIO/RMS-dependent code will hopefully be compatible. <br>
<br>
> I haven't said that FreeVMS has to be only a 64 bits OS. I have
written that _in a first time_, we have to write a runable and stable
system on only one arch.<br>
<br>
Hopefully we can all agree on x86? I don't exactly have a SPARC machine
laying around...<br>
<br>
Graham's resources will be quite interesting to read and design
according to - I will take note of them this weekend during my next
long coding session for this project. <br>
<br>
> Any special tool you will use for documentation? (Like doxygen,
kernel-doc)?<br>
<br>
...ASCII? <br>
<br>
In all seriousness, I have written my documentation in plain text in my
IDE (Geany) as well as in-code comments clarifying functions and kernel
interfaces. I don't like formats like PDF or DocBook (SGML) because
they aren't all that portable and, frankly, a pain in the ass to read
when running console-only or without a proper interpreter. <br>
<br>
Since we have a wiki, I vote for plaintext documentation with the easy
conversion to wiki-markup later by human hands as we make the
documentation public outside of the source code. If anyone has any
other ideas, let them be heard, but I'm just shooting for simplicity
and portability but I want to get the code properly documented without
detracting too much from the actual coding, and the in-IDE ASCII
editing allows me to do that while acheiving full portability.<br>
<br>
But I'm not saying I'm closed to other options, as long as they are
simple to use and in a portable format. <br>
<br>
-AC<br>
</div>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
FreeVMS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:FreeVMS@rayleigh.systella.fr">FreeVMS@rayleigh.systella.fr</a>
<a class="moz-txt-link-freetext" href="https://www.systella.fr/cgi-bin/mailman/listinfo/freevms">https://www.systella.fr/cgi-bin/mailman/listinfo/freevms</a>
</pre>
</blockquote>
<br>
</body>
</html>