Date: Mon, 18 Mar 1996 13:15:45 -0500 From: Charles Henrich <henrich@crh.cl.msu.edu> To: phk@critter.tfs.com, freebsd-hackers@freebsd.org Subject: Re: CFV: adding phk_malloc to -stable Message-ID: <199603181815.NAA06127@crh.cl.msu.edu> References: <4ijdlv$qg1@msunews.cl.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In lists.freebsd.hackers you write:
>> > Until you can demonstrate that NOTHING is (more) broken by doing so,
>> >
>> > I VOTE NO!
>>
>> Following this reasoning, you will not allow any extension whatsoever
>> to the kernel or system libs or other critical parts of the system,
>> because you often cannot demonstrate what you ask.
>>
>> > Stable is supposed to be just that -- stable. You cannot go breaking things
>> > that work, even if they work only because of "two wrongs"
>I think Richard is getting too defensive here, though his position is
>understandable.
>I belive that all the code that has been report as broken has been fixed in
>both -current and -stable, with the possible exception of the NIS/YP stuff.
>The issue is still up in the air, and for it to be decided we need some,
>actually: a lot, of reports saying: I'm running phkmalloc in -stable and
>it works fine.
>So here is again the recipe:
> 1. get src/lib/libc/stdlib/malloc.[3c] from -current and stick it
> into your -stable source tree.
> 2. make world.
> 3. beat on it A LOT
> 4. report result.
>In particular I'd like reports from people running NIS/YP.
If Im running 2.1-R, is there any easy way to get your malloc without having
to rebuild the OS from source? Drop in a prebuilt libc.a maybe? If someone
could give me a tar file with the necessary files I would be more than happy to
use it.
-Crh
--
Charles Henrich Michigan State University henrich@msu.edu
http://pilot.msu.edu/~henrich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603181815.NAA06127>