[Coco] Play with NitrOS-9 over the Internet

[Aaron Wolfe]

On Mon, Dec 28, 2009 at 1:34 PM, Joel Ewy <jcewy at swbell.net> wrote:
> Aaron Wolfe wrote:
>>
>> Thanks to your listing of a massive file last night, and the resulting
>> unresponsiveness of Boisy's coco, I was inspired to rewrite the
>> routines for deciding who gets a turn at sending data over the virtual
>> channels.
>>
>>
>
> Cool.  (I guess that 'your' is directed at me...)  Glad my fumbling
> exploration could inspire an improvement.
>
> Do we have any way to kill the running process yet?  Dibble and Pucket say
> that <ctrl>e should work if you don't have a CoCo keyboard's <break> key on
> you.  <ctrl>c is a popular choice as well...

You can set the eof character with tmode, it seems to break out of some things.
Boisy updated the device descriptors to use 1B for eof by default,
which is usually what you get by hitting ESC.  It isn't perfect and we
don't have proper signals working yet, but sometimes it works.   If
ESC doesn't work you could try changing it with something like:

tmode eof=XX

where XX equals the value of the key you want to use..

-Aaron


>
> JCE
>
>> This situation will not happen again.  Interactive sessions (users
>> typing things, basically) now have priority over bulk transfers.  Each
>> port ages when it doesn't get to send during a poll, and the oldest
>> port interactive port always gets to send.  This promotes fairness
>> even amongst equally interactive sessions.  Bulk ports only send when
>> no interactive ports have data waiting, and still go in aged order to
>> smooth things out.
>>
>> The end result is that you can now do a large data transfer and
>> continue to use other terminals with minimal slowdown.  I can actually
>> do three wget's of large websites, FTP transfers or server file
>> listings all at the same time and am still able to use a fourth
>> terminal, although at that point it gets pretty tedious :)  The Coco
>> is awesome, OS-9 is amazing, but there is only so much she can do "at
>> one time", although this limit is surprisingly high.  I've often
>> thought I'd hit a performance barrier only to find it is my code that
>> is limiting throughput, not the Coco.
>>
>> I believe the new traffic shaping routines are live on Boisy's Coco.
>> Combined with bug fixes (my mistake!) in the OP_WRITE routine and some
>> other optimizations in the server, it is now quite practical to use
>> wget to transfer the contents of most any URL directly to a file on
>> your Coco (or display on the screen, wget writes to stdout).
>> Performance in interactive sessions, especially with multiple
>> sessions, should be noticeably improved.
>>
>>
>> -Aaron
>>
>>
>>
>>
>>
>> On Sun, Dec 27, 2009 at 10:38 PM, Joel Ewy <jcewy at swbell.net> wrote:
>>
>>>
>>> Well, I did a "dw list dw.log".  It's still on December 23.  <ctrl>c
>>> doesn't
>>> abort it.  I could kill my telnet, but I guess the OS-9 Process would
>>> keep
>>> running?
>>>
>>> JCE
>>>
>>> Boisy G. Pitre wrote:
>>>
>>>>
>>>> Aside from Aaron, Jim and I attempting this (with slightly buggy
>>>> software), this is probably a first.
>>>>
>>>> If you want to play around with NitrOS-9/6309 Level 2, then telnet to my
>>>> system.  I have tsmon running on ports t0-t6, although t0 isn't working
>>>> for
>>>> some reason.  That leaves 6 ports that can be in use simultaneously.
>>>> Press ENTER when connected.  You should see the tsmon login prompt,
>>>> though
>>>> depending on how other users disconnected, you may see a shell prompt
>>>> when
>>>> you press ENTER.
>>>>
>>>> To get to it:
>>>>
>>>> telnet aes.dyndns.org 6809
>>>>
>>>> Good luck and please let me know how it works.
>>>> --
>>>> Boisy G. Pitre
>>>> http://www.tee-boy.com/
>>>>
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>
>>>>
>>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>