See below.
At 07:32 PM 6/4/00 -0400, David Aikema wrote:
>I've got two questions:
>1. Currently we've got a internet call director package from the local
telco ( the client was originally downloaded from
http://bctel.internetcalldirector.com ) However the telco name has changed
since the signup and as well the only page offered there seems to be a
signup sheet. I punched in www.internetcalldirector.com hoping for
something more, and it redirected me to www.internetcallmanager.com. I
checked out their list of clients and noticed that they only offered them
for windows and macs. Has a clone of this software been developed for linux?
I looked briefly at this WEb site but still couldn't quite figure out what
the products does. Perhaps if you'd describe what it does, someone can then
tell you if there is something similar for Linux.
>2. Also, we have an old 386sx25 machine lying around the house (4 megs 30
pin ram, 28.8k modem, sb pro v.2 sound, creative labs 1x cd-rom... ~ 100mb
hd). Currently we're using one of our windows machines running proxy+ for
internet access over the lan. However I sorta would like to eliminate this
and use the 386 if possible instead. I noticed that one of the ethernet
cards I have seems to fit the machine.
>However, I'm guessing that the machine doesn't have enough ram for much of
anything.
Certainly not anything mainstream (sorry, Lawson!). The router distro I know
best, LRP (www.linuxrouter.org or lrp.c0wz.com) requires 12 megs to run
well, because it runs from a RAM disk. A hard-dist-based distro might work in 8.
However ... just how adventurous are you feeling? If all you want the thing
to do is to NAT (Masq) and run a basic set of ipchains, you might try a
trick I've read about but never myself tried. Do a stripped down, 4 meg
install (read Lawsons's stuff here). Run it so that it starts, sets up your
routes, your NAT'ing, and your chains ... then shutdown.
Shutown stops all *processes*, including init, but the kernel itself remains
active. Since NAT'ing and routing are done in kernel space, the box
continues to route. This is probably more a stunt than a real routing
method, but who knows?
>I've looked at numerous other mini distros of linux and noticed that most
seem to require a minimum of 8 - 16 mb of ram.
Most do require at least 8, because most are syslinux/ramdisk based. I think
there are some that are not. Look at http://linux-embedded.org for leads.
>However, I have no idea where I'd be able to pickup ram of this type anymore.
I recently saw it advertised cheap at www.computergeeks.com .
>Another limitation for this machine would be that of a monitor. It's
monitor was 'stolen' for use by one of our other computers.
You don't need a monitor for everyday use; it will mostly sit somewhere
hidden away, merrily ruting for you.
>Basically I'm wondering if it could manage to act as a gateway machine
(socks server too... as well as compatibility for #1)
Probably not. The only way, as Lawson said, would be by using swap heavily
... but routing activities have to happen fast, and swap isn't realtime.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
