Lynx port for ELKS underway!

[Jody <jbruchon@nc.rr.com>]

Greetings to all.

I am not an experienced C programmer.  I have no practice writing my own 
code.  However, I am learning a lot in the process of cleaning up a copy 
of the Lynx2-2 package so that it will be easier to port, if porting 
Lynx is truly possible (hey, if you whack out all the crap you don't 
need, it looks like Lynx gets a LOT smaller!).

First of all, this message is intended primarily to announce a few things.

A. I am working on cleaning Lynx up for porting to compile with bcc.
B. I don't know how to do it but I'll figure it out
C. Help would be appreciated if available, particularly with .h file 
substitution (netdb.h, etc)
D. ELKS is very much alive!

The current phase I call the "idiot phase" because even a C-inept idiot 
like me can do it.  I am cleaning out the compatibility code and 
commentary that allows compiling on such systems as AIX, NeXT, Ultrix, 
and SCO (cough, heretics, cough!), and VMS(!).  As of this moment (Sept. 
20, 2004, 12:52 AM EDT) I have already cut out 368317 bytes of data from 
the source, and considering the original source is 1496674 bytes, that's 
a lot of garbage gone (24.6% to be exact, almost 1/4 of the ENTIRE code 
base for Lynx2-2!!!!)

Once I finish wiping out code for things like TN3270, newsgroups, and 
telnet/rlogin protocols (leaving FTP and HTTP only) we should have 
something more useful to play with.  At that point, I will make the 
cleaned code available in a tarball somewhere for all to pick at, 
because in all honesty I would love to be the hero that ports Lynx to 
ELKS but I don't have enough knowledge to do it all alone.

I know that all of you would LOVE to have "Lynx86" and I will do my best 
to achieve that, or at least give it a hefty push.

Where the heck is netdb.h?

Best wishes to all,
--- Jody ---