On Wed, 1 Sep 1999 08:40:30 +0700, Eko Priono wrote:
EP> Linux-Xterm can provide both *multitasked* internet and
EP> access to Linux itself and it's applications.
True, but this requires a powerful Pentium-class computer to
drive the system. The 100% survPC alternative still uses a
Linux computer as the server (but the CLI setup is MUCH less
resource-hungry). Since this server is running Linux, it
happily multitasks. This means that the DOS clients have
the option of telnetting to the server and running Linux
and it's applications. In fact, herc clients (which can't
run Arachne at the moment) will still be able to access the
internet by telnetting to the server and using Lynx there.
This approach will also provide faster browsing for old XTs
and 286s.
EP> Linux is still the best candidate for "the next
EP> generation platform" and worth to learn for.
I agree. But you don't need a "next generation" computer
to use Linux. It works well on old 386s (as long as you
have 8meg RAM and stick to CLI).
SD> The problem with your X-terminal approach is that it
SD> requires a powerful Pentium-class server to do the processing.
EP> Is Linux has support for distributed (paralel) processing?
EP> If so, then you should be able to substitute that single
EP> powerful P-class server with several networked 486s.
Yes, distributed processing is possible under Linux, but you
need a high-speed network to make it viable. Such a network
would be MUCH more expensive than using survPC ethernet cards
and coax. Moreover, distributed processing (via network)
carries a significant overhead and is not beneficial for every
application.
EP> However, even might a lot more cheaper, this approach still
EP> less effective. Since DOS Arachne by nature is single-tasking,
EP> "overbooking" situation still happened when you wait for page
EP> download. In other hand, you could request multiple pages at
EP> once, with X-terminal approach; while doing something else on
EP> the same time (reading previous page, writing mail, chatting,
Actually, Arachne does do some primitive multi-tasking. It does
multiple requests for packets (which speeds things up a lot) and
it allows you to download a page in the background while you are
reading the current page.
EP> BTW, seems you have real-world experience on Linux-Arachne
EP> setup? ;) How about posting a "complete idiot's guide" on
EP> that subject?
1) Install CLI Linux on your server. Make sure your your
kernel includes NET, FIREWALL, INET, IP_FORWARDING, IP_FIREWALL,
and IP_MASQUERADE. This is pretty standard stuff. For example,
it's included in the default Slackware kernel (bare.i).
2) Set up your local network. Use DOS packetdrivers on your
clients and ping the server. Once this is working, install a
DOS telnet on the clients and try logging into the server.
3) Set up ppp on the server. Do some browsing with Lynx. Log
into the server with your clients and browse with Lynx.
4) Install Arachne on the clients and set it up using the
network parameters. Activate IP masquerading on the server
(for 2.0.x kernels it's called ipfwadm). ppp-on. Run Arachne
on the clients.
BTW, each of these steps will take several hours for newbies.
Or several days (weeks?) if you are unlucky. The important
thing is not to get discouraged. Just take it step by step
and you will get there eventually. Feel free to contact me
if there are any hangups.
Cheers,
Steven
-- Arachne V1.50;beta, NON-COMMERCIAL copy, http://home.arachne.cz/
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.
