hammer wrote:
>
> >
> > The alternative (my alternative) is to use the server as a TCP/IP router
> > and let each of the clients do its own processing (with Arachne). In this
> > case an ordinary 486 (or even a high- end 386) running CLI Linux can be
> > used as the server.
> -------------------unquote.-------------
>
> Though for the "house ISP coop" this does pose a problem: sure some of
> the participants want/are used to use the N$/M$ bloatbrowsers. -hc
Actually, the Linux gateway just routes the TCP/IP. It doesn't care
whether it's from Arachne or from N$/M$ bloatbrowsers.
The quote above related to a "cybercafe" using survivor PCs as clients.
I suggested using Arachne on the client machines because this gives
better performance on survPCs than the more bloated browsers. However,
if your house ISP clients are using up-to-date computers, then they
should be able to use N$/M$. Just don't ask me how to set up TCP/IP
for M$Windows. I've successfully used DOS and Linux broswers on my
"cybercafe" clients, but I don't know anything about M$Windows.
Cheers,
Steven
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
