Return to BSD News archive
Xref: sserve comp.os.linux:34661 comp.os.386bsd.questions:1683 Newsgroups: comp.os.linux,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.uoregon.edu!netnews.nwnet.net!news.u.washington.edu!serval!hlu From: hlu@eecs.wsu.edu (HJ Lu) Subject: Re: Summary of Linux vs. 386BSD vs. Commercial Unixes Message-ID: <1993Apr17.194341.4562@serval.net.wsu.edu> Sender: news@serval.net.wsu.edu (USENET News System) Organization: School of EECS, Washington State University References: <1993Apr15.225354.18654@samba.oit.unc.edu> <1qo0lq$1hm4@hal.gnu.ai.mit.edu> <1993Apr17.161516.2794@serval.net.wsu.edu> <1qpk76$bbl@hal.gnu.ai.mit.edu> Date: Sat, 17 Apr 93 19:43:41 GMT Lines: 30 In article <1qpk76$bbl@hal.gnu.ai.mit.edu>, mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes: |> |> In article <1993Apr17.161516.2794@serval.net.wsu.edu> |> hlu@luke.eecs.wsu.edu (HJ Lu) writes: |> > |> > 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. |> |> Why are you trying to confuse the issue? Yes, Linux will (and has) |> taken things from 386BSD when it's convenient. Likewise, 386BSD will |> (and has) taken things from Linux. |> |> You make it sound like 386BSD *can't* use code from Linux. This is No. I am trying to say the "official" 386bsd release is not willing to use GNU copyrighted code. Of courses, you can make/release your own 386bsd :-). I know you have done that for yourself. |> bogus. It's just very carefully chosen which parts are worthwhile, ^^^^^^^^^^^^ That means no GNU copyrighted code in the "official" 386bsd release. BTW, I'd love to see the "official" 386bsd release uses GNU copyrighted code. |> which aren't, and which need to be redone. |> H.J.