Date: Mon, 18 Mar 1996 09:52:56 +0000 From: Poul-Henning Kamp <phk@critter.tfs.com> To: Luigi Rizzo <luigi@labinfo.iet.unipi.it> Cc: rkw@dataplex.net (Richard Wackerbarth), stesin@elvisti.kiev.ua, hackers@FreeBSD.ORG Subject: Re: CFV: adding phk_malloc to -stable Message-ID: <7645.827142776@critter.tfs.com> In-Reply-To: Your message of "Mon, 18 Mar 1996 10:30:04 %2B0100." <199603180930.KAA00195@labinfo.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7645.827142776>