Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!olivea!grapevine.lcs.mit.edu!ai-lab!life.ai.mit.edu!mycroft From: mycroft@trinity.gnu.ai.mit.edu (Charles Hannum) Newsgroups: comp.os.386bsd.questions Subject: Re: ???BSD??? Date: 02 Sep 1993 19:40:41 GMT Organization: MIT Artificial Intelligence Lab Lines: 38 Message-ID: <MYCROFT.93Sep2154041@trinity.gnu.ai.mit.edu> References: <263f2e$aod@eddie.mit.edu> <265ei6$7qs@pdq.coe.montana.edu> NNTP-Posting-Host: trinity.gnu.ai.mit.edu In-reply-to: osyjm@cs.montana.edu's message of 2 Sep 1993 18:37:58 GMT In article <265ei6$7qs@pdq.coe.montana.edu> osyjm@cs.montana.edu (Jaye Mathisen) writes: Linux Runs well in 8MB's of RAM, 100 MB's of disk (I have oodles left). Just a point of reference here: I do most of my NetBSD work on a 386 with 8MB of RAM, and except for compiling a particular file in CLISP, I have never had problems. (That file seems to make GCC 2 consume a very large amount of memory; perhaps this will be fixed by GCC 2.5.) The same machine also acts as a NFS server for a HP 370 (also running NetBSD) and a Sun 3 (running a totally new and horribly incomplete port of NetBSD, so don't ask B-)). X runs fine. I don't normally run X on it, as the video card sucks. (It does work, though.) I do run Emacs 19 using a different display. So just in case anyone really thinks NetBSD needs gobs up memory, let's enumerate all this. My 386, with 8MB of RAM, normally runs at least the following: * all the standard shit--sendmail, lpd, inetd, rwhod, plus amd and xntpd. * NFS server for two machines * Emacs 19 * GCC 2 (sometimes with another GCC bashing on the disks over NFS). and it works fine. Actually, I'd be hesitant to switch to another machine, as this one has been rock solid for a few of months now.