From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 01:47:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A83B916A4CE for ; Fri, 6 Feb 2004 01:47:45 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8551043D45 for ; Fri, 6 Feb 2004 01:47:42 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc13) with ESMTP id <2004020609474201500jqsg4e>; Fri, 6 Feb 2004 09:47:42 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id BAA24957 for ; Fri, 6 Feb 2004 01:47:40 -0800 (PST) Date: Fri, 6 Feb 2004 01:47:39 -0800 (PST) From: Julian Elischer To: FreeBSD current users In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: FreeBSD 1.1 under -current :-) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 09:47:45 -0000 On Fri, 6 Feb 2004, Julian Elischer wrote: > > well this is not really a -current question, but.. > I unpacked a freebsd 1.1 cdrom into a subdirectory > and after kldloading the aout module, chroot'd into it.. > [...] > > then it all blows up.. > > does anyone remember if there was an extra step we used to have to do? > did we have to have a populated /usr/obj to start with? > if so where did we get it from? > I've tracked it down to mkdir -p not being able to work. does anyone remember if there was a change to statfs or fstat or similar that would stop a 1.1 binary from working correctly? interestingly, I think this MAY have.....worked about 9 months ago.. I ran into the 30000 PID problem previously doing a make world and I think it got beyond this point. my guess is that someone has broken "old.stat" as it never even tries to do a NAMEI.