What has happened to this list? The last message I received in my mailbox
was
June 3. Since then, nothing. Has it truly been this quiet, or is it ANOTHER
one
of the on-going problems I have with my ISP?
==
Never cross a dragon - for you
I really don't see where this is a problem. User level processing does not
need
hardware memory protection; it could be implemented as a strictly software
solution. For example, a table defined within the OS giving the user and the
level. Then, all memory access could interrogate this table and
Taken from the ELKS web site - road map page
After 0.1 more elaborate features will be added, in particular
networking. At this stage it may be desirable to maintain a 0.1 stable
series, and do all new development in the 0.2 series. It may reduce
confusion to maintain the convention of
Greg Haerr wrote:
I have spent considerable effort trying to make sure that the Microwindows
system will run on 16 bit systems, and it should continue to do so,
although currently the application must be bound with the server
since we lack UNIX sockets. This limits the application size.
Is the TCP/IP project totally dead, or is someone still working on it?
I have an ATT PC6300 just waiting for me to install ELKS on it, but
without a TCP/IP stack, it is of limited use to me. I **really**
want to put it back into service!! Thanks - Larry
--
Alan Cox wrote:
> hybrid crossing between the V7 and the linux method.
Like allocating a
> relatively small struct, but then make it an option to grow the struct
by
> making a linked list of these structs. Given the low computative
power of
The struct size is fixed - I dont follow you
If I
