Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!newsfeed.internetmci.com!raven.eva.net!bighorn.accessnv.com!jca From: jca@bighorn.accessnv.com (J.C. Archambeau) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: AMD 386sx with 4 megs; can it be done? Date: 4 Dec 1996 20:13:43 GMT Organization: Access Nevada Inc. Lines: 30 Message-ID: <584m1n$hu4@raven.eva.net> References: <57oa8i$nbs@agate.berkeley.edu> <b58_9611301919@usbbs.com> <58398a$3cg@Symiserver2.symantec.com> NNTP-Posting-Host: bighorn.accessnv.com X-Newsreader: TIN [version 1.2 PL2] tedm@agora.rdrop.com wrote: : > bp> First of all, is FreeBSD known to work on AMD : > bp> 386sx systems with 4 megs of RAM? Regarding the original question. You can try it, with a large swap space. :) I wouldn't want to run X on it though nor is it exactly the most fork bomb resistant piece of hardware. :D : I ran 1.1, and am currently running 1.1.5.1 on a 386/20 with 8MB for as : long as it's been out. (several years) I'm using it as a mailer, while : it's slower than my 486/133 it's never crashed. I was using a 386SX. : I recently swapped the SX board for a 386/DX 25Mhz board with 8MB ram : (whoee, a whole 5 Mhz! ;-)) just to see what would happen and the system : runs twice as fast. It's pretty amusing as the 386/DX board is about : 3 years older, and has all DRAM memory on it, while the SX had SIMMS. Not all that surprising since you have essentially doubled the throughput of CPU to memory operations by bumping the data bus from 16-bit (SX) to 32-bit (DX). It doesn't really matter if the memory is in SIMMs or DRAMs it isn't going to affect the performance. -- /* ** Internet: jca@accessnv.com | Don't blame me, I didn't vote for Clinton. ** jca@anv.net | Intel is the word for 'errata.' *************************************************************************** ** Note: Please direct all unsolicited commercial e-mail (Spam) to the ** special account support@accessnv.com. Thank you. *************************************************************************** */