Re: Status Report from Rochester

[Stupendous Man <richmond@a188-l009.rit.edu>]

  Chris Albertson makes a couple of good points about my effort
to write a Mark IV control program:

> I would send commands to your program if we (any of us on
> this list) can think of how to do two things:
>
>  1) Have Michael's program accept commands via some
>  inter process communication interface. (I'd prefer sockets
>  but a FIFO Pipe would be easier.)

  Yup, an option for the program to communicate with the 
user via sockets would be a Good Thing.  It's on my list.
I'd like to retain the current options of direct keyboard
input, and reading commands from a file, too.
(Of course, if someone wants to add a socket I/O option
before I get to it, I won't complain ...)

> Will you have time to coordinate these changes? 
> There are a few ways to do this
> 
> 1) "The way Linus works the Linux kernel"
> People send Linus changes.  He reads and accepts or rejects
> each change or possibly re-writes it himself.  This is the
> "one guy in charge" method.  

  I'd prefer this model.  If you're interested in helping
out, just grab a copy of the code, make your changes, and 
then contact me.  I'll try to keep a master copy on my machine
here; perhaps I'll manage to set up a CVS repository from which
outside users can check out.

                                        Michael Richmond