From owner-freebsd-hackers Mon Mar 10 18:50:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA20326 for hackers-outgoing; Mon, 10 Mar 1997 18:50:37 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA20321 for ; Mon, 10 Mar 1997 18:50:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09675; Mon, 10 Mar 1997 21:50:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 10 Mar 1997 21:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id UAA05259 for ; Mon, 10 Mar 1997 20:49:48 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA22402 for freebsd-hackers@freefall.cdrom.com; Mon, 10 Mar 1997 20:55:45 -0500 (EST) Date: Mon, 10 Mar 1997 20:55:45 -0500 (EST) From: Thomas David Rivers Message-Id: <199703110155.UAA22402@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: 2.2-GAMMA (3/10/97) and the "dup alloc" problem. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just to report in on the question of "does the latest 2.2-GAMMA (3/10/97) exhibit the 'dup alloc' problem". I have just tried out the boot floppies that were made this morning; the problem still exists. - Dave Rivers -