Return to BSD News archive
Xref: sserve comp.os.linux:34604 comp.os.386bsd.questions:1669 Newsgroups: comp.os.linux,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.uoregon.edu!netnews.nwnet.net!news.u.washington.edu!serval!luke.eecs.wsu.edu!hlu From: hlu@luke.eecs.wsu.edu (HJ Lu) Subject: Re: Summary of Linux vs. 386BSD vs. Commercial Unixes Message-ID: <1993Apr17.161516.2794@serval.net.wsu.edu> Sender: news@serval.net.wsu.edu (USENET News System) Organization: Washington State University! References: <1993Apr15.225354.18654@samba.oit.unc.edu> <1qo0lq$1hm4@hal.gnu.ai.mit.edu> Date: Sat, 17 Apr 93 16:15:16 GMT Lines: 18 In article <1qo0lq$1hm4@hal.gnu.ai.mit.edu> mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes: > >In article <1993Apr15.225354.18654@samba.oit.unc.edu> >Brandon.Vanevery@launchpad.unc.edu (Brandon Vanevery) writes: >> >> 386BSD has better TCP/IP, for now. >> >> Linux is far less resource-hungry, due to shared libraries. > >For now. > Linux will use whatever better in 386bsd. But 386bsd has to start from scratch, unless you do it yourself. For example, 387 emulation and C library. H.J.