<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
Your research seems "on the mark" Maiko.<BR>
<BR>
On Thu, 2006-09-14 at 12:00 -0500, Maiko Langelaar (ve4klm) wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Greetings,</FONT>
>>SNIP<<<FONT COLOR="#000000"> The latest GCC and GLIB do not</FONT>
<FONT COLOR="#000000">support the SETJMP and LONGJMP (in that it's hidden from the programmer</FONT>
<FONT COLOR="#000000">now).</FONT>
</PRE>
</BLOCKQUOTE>
Isn't this a "natural progression"?<BR>
With early DOS development, the system had few responsibilities and the application had many.<BR>
With late Linux & MS-Win the kernal and drivers automate much to reduce the application responsibilities.<BR>
Perhaps jnos suffers today from neglect (I hate that word actually) to remain current year by year thru that progression?<BR>
<BR>
Even though jnos consumes few CPU cycles making multi-core processors and cluster computing unnecessary, that is the direction processors and languages are trended. You started a (in my opinion) a good thing when you set the stage for using library calls to replace native code. Perhaps THREAD is just another part of that modernization process? And there is an (endless?) set of related issues: Barrys directory structure, executing jnos in user space / not root space, simplify & automating installation... In saying that I don't mean to understate the labor involved.
<BLOCKQUOTE TYPE=CITE>
<PRE>
</PRE>
</BLOCKQUOTE>
>>SNIP<<
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">So there you have it, some challenges for NOS in general, as operating</FONT>
<FONT COLOR="#000000">systems progress further and further, and system internals are more</FONT>
<FONT COLOR="#000000">and more hidden from the programmer as time goes on ...</FONT>
</PRE>
</BLOCKQUOTE>
MANY projects are known to reach a point in feature development and stop for a "housekeeping".<BR>
After the code is restructured (not a menial task) development continues often more rapidly.<BR>
Sounds like you may be announcing jnos / nos has reached a similar point?<BR>
<BR>
As a side-thread LINUX FORMAT Sept 2006 page 46 has a very interesting article titled "GET SPIKED".<BR>
The focus is to validate the stack of application, platform, and hardware. In jnos case the approach to validation automates a test suite for all the varieties you choose to support, and all the features you choose it install. They describe a heads-up business plan...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Maiko Langelaar / VE4KLM</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
jnos is a great tool.<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de George (Skip) VerDuin K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>