> I'm getting conflicting reports on running Linux on a 386sx-40...
> in Linux: Getting Started (which came w/ "slackware 2.2") it claims that
> a 386sx is fine (specifically noting even the lowly 386sx-16
There does not seem to be any problem with this setup - If anything fails turn
off ram caching though - this MIGHT help with some of the weirder chipsets.
I have used linux on a 386sx16 without problems. There's no reason you couldn't
start up XWindows even - if your patient.
Quote:> in Linux Configuration & Installation (2nd edition includes Slackware96
> (2.0 Kernel)) it says don't even bother to try.
Because if you've bothered to plunk down the money for the book, odds are you
have the reletively small amount of money to buy an upgrade: consider that I
only paid $160 for my AMD 5x86 133 with 16MB Ram onboard PCI dual IDE, 2 16550A
serial ports, etc etc etc and at the same show I saw 40Mhz 386 systems going
for as little as $30 - throw on 8MB of ram and your set...
Quote:> what I want to do is setup the drives (2 512M scsi drives on a
> aha-1542F) and then move the drives/controller into a more capable
> machine....probably a 486DX2-66 (yea...the idea is to run linux on the
> orphan at least for a while).
You will notice that certain things feel faster under linux on a 386sx40 than
under DOS/Win on a 486DX2-66. I specifically refer to editing text files while
using the modem, etc. Dos/Win actively wastes processor cycles!
Neat Cx486SLC trick: start your CPU under DOS, see how hot it gets in 10
minutes (burning!). Redo the test in linux (room temp!). Now start compiling a
kernel and see that the processor gets kinda warm (like a kid with a lowgrade
fever). Thermal Load Averaging!
> Linux - the answer to the microsoft problem
/ _ _ |_ _ _ _|
Dogs crawl under fences, applications crawl under windows
Their address sums up their attitude: 1 Microsoft Way
"By US Code Title 47, Sec.227(a)(2)(B), a computer/modem/printer meets the
definition of a telephone fax machine. By Sec.227(b)(1)(C), it is unlawful to
send any unsolicited adverti*t to such equipment. By Sec.227(b)(3)(C),
a violation of the aforementioned Section is punishable by action to recover
actual monetary loss, or $500, whichever is greater, for each violation."
I pay $18/month for my ISP connection. I have a 14.4K PPP connection. All
incoming unsolicited commercial traffic will therefore be billed at a rate of
$.01 per 1.5Mbyte, or $500, to compensate loss of service.