From owner-cvs-include  Tue Nov 15 09:02:32 1994
Return-Path: cvs-include-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id JAA09248 for cvs-include-outgoing; Tue, 15 Nov 1994 09:02:32 -0800
Received: from precipice.Shockwave.COM (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA09242; Tue, 15 Nov 1994 09:02:26 -0800
Received: from localhost (localhost [127.0.0.1]) by precipice.Shockwave.COM (8.6.9/8.6.9) with SMTP id JAA02575; Tue, 15 Nov 1994 09:01:17 -0800
Message-Id: <199411151701.JAA02575@precipice.Shockwave.COM>
To: Nate Williams <nate@bsd.coe.montana.edu>
cc: "Andrew A. Chernov" <ache@freefall.cdrom.com>,
        CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com
Subject: Re: cvs commit: src/include malloc.h Makefile 
In-reply-to: Your message of "Tue, 15 Nov 1994 09:53:38 MST."
             <199411151653.JAA09195@bsd.coe.montana.edu> 
Date: Tue, 15 Nov 1994 09:01:16 -0800
From: Paul Traina <pst@shockwave.com>
Sender: cvs-include-owner@FreeBSD.org
Precedence: bulk

Why would we want the system5 fatmalloc?  Why do we want malloc() at all?

Did our name change to FreeUnivel?

  From: Nate Williams <nate@bsd.coe.montana.edu>
  Subject: Re: cvs commit: src/include malloc.h Makefile
  > ache        94/11/15 05:42:21
  > 
  >   Modified:    include  Makefile
  >   Added:       include  malloc.h
  >   Log:
  >   Add malloc.h for better SYSV/Linux compatibility like most
  >   providers (like SUN f.e.) does.
  >   malloc.h have comment about its SYSVism
  
  Umm, in your reply to me, you said you were going to fix the ports
  that require it.  If you are just going to add 'malloc.h', why
  don't you add the libmalloc stuff from 1.1.5?