home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
- From: terry@cs.weber.edu (A Wizard of Earth C)
- Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
- Message-ID: <1993Jan1.102032.8413@fcom.cc.utah.edu>
- Sender: news@fcom.cc.utah.edu
- Organization: Weber State University (Ogden, UT)
- References: <JKH.92Dec31154004@whisker.lotus.ie>
- Distribution: comp
- Date: Fri, 1 Jan 93 10:20:32 GMT
- Lines: 23
-
- In article <JKH.92Dec31154004@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
- >I say we petition Bill to use GNU malloc in preference. Most folks aren't
- >going to know enough (or dare) to replace malloc in libc themselves, but
- >they will notice the very painful state of affairs that trying to work
- >in a low memory environment brings; why not spare them the pain?
-
- If we are going to vote, I vote for one of the PD malloc implementations
- as opposed to the GNU copyleft implementation. There are many reasons,
- some stated by Lynne and Bill, for keeping 386BSD salable without sources;
- GNU copyleft ruins this.
-
-
- Terry Lambert
- terry@icarus.weber.edu
- terry_lambert@novell.com
- ---
- Any opinions in this posting are my own and not those of my present
- or previous employers.
- --
- -------------------------------------------------------------------------------
- "I have an 8 user poetic license" - me
- Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
- -------------------------------------------------------------------------------
-