[Coco] Full GUI DriveWire 4 beta

[Aaron Wolfe]

inetd is pretty important, it is the primary way to access NitrOS9
programs and shells from other computers across a network.  I think it
used to be part of the nightly build at one point, maybe it is failing
there as well.

there are a handful of tools that are sort of part of DriveWire and
sort of part of NitrOS9.. inetd, the telnet client, the http server,
etc.  I'd love to see these support multiple networking solutions and
be a sort of standard set of tools for all NitrOS9 users, but right
now DriveWire is the only way to do such things.

I guess the question is should we be building inetd, telnet, httpd,
etc as part of the NitrOS9 disks?  Or maybe as a seperate "extras"
disk?  I can probably sort out the build process to do whatever is
acceptable.

-Aaron


On Mon, Dec 27, 2010 at 10:42 PM, Robert Gault <robert.gault at att.net> wrote:
> Aaron,
>
> There one more issue that should be cleared up. Inetd is, I think, part of
> the DW4 code. It is not included in the nightly builds of NitrOS-9, it is
> not on the DW4 extras disk, and it won't compile for me from the NitrOS-9
> source code because of an rlink error.
>
> Now I can see that maybe inetd won't build with a Windows mingw msys system
> but if it works for anyone, it ought to be in the nightly build. Just how
> important is this module?
>
> Robert
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>