From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 13:14:30 2003 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 5BF0016A4CE for ; Thu, 13 Nov 2003 13:14:30 -0800 (PST) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43CFE43F85 for ; Thu, 13 Nov 2003 13:14:27 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1]) hADLEMNJ089733; Thu, 13 Nov 2003 23:14:22 +0200 (SAST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.12.9/8.12.9/Submit) id hADLEK0n089732; Thu, 13 Nov 2003 23:14:20 +0200 (SAST) (envelope-from jhay) Date: Thu, 13 Nov 2003 23:14:19 +0200 From: John Hay To: Bruce Evans Message-ID: <20031113211419.GA89455@zibbi.icomtek.csir.co.za> References: <20031113075722.GA64129@zibbi.icomtek.csir.co.za> <20031114062238.M3230@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031114062238.M3230@gamplex.bde.org> User-Agent: Mutt/1.4i cc: current@FreeBSD.org Subject: Re: new kernel and old programs - bad system call 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: Thu, 13 Nov 2003 21:14:30 -0000 On Fri, Nov 14, 2003 at 06:38:28AM +1100, Bruce Evans wrote: > On Thu, 13 Nov 2003, John Hay wrote: > > > Is it ok to run a new kernel (after the statfs changes) and older > > programs? I thought so from what i gathered out of the commit > > messages, but my test box doesn't like it at all... Well except > > if something else broke stuff: > > I have no problems with a current kernel and an old world. > > > ###### > > ... > > Mounting root from ufs:/dev/da0s1a > > pid 50 (sh), uid 0: exited on signal 12 > > Enter full pathname of shell or RETURN for /bin/sh: > > # ls > > pid 56 (ls), uid 0: exited on signal 12 > > Bad system call > > # > > ###### > > Maybe you don't have old programs. Unfortunately, even /bin/sh is > affected by the changes (it has a reference to fstatfs). I'm pretty sure it is old binaries because they work with my old kernel: beast# ls -l /bin/*sh* /boot/kernel.work/kernel /boot/kernel/kernel -r-xr-xr-x 2 root wheel 879252 Nov 11 14:52 /bin/csh -r-xr-xr-x 1 root wheel 751752 Nov 11 14:52 /bin/sh -r-xr-xr-x 2 root wheel 879252 Nov 11 14:52 /bin/tcsh -r-xr-xr-x 1 root wheel 2673454 Nov 3 09:17 /boot/kernel.work/kernel -r-xr-xr-x 1 root wheel 2758305 Nov 13 09:01 /boot/kernel/kernel The binaries work just fine with kernel.work but not with kernel. Maybe I should try a few other things, like a UP kernel. Luckily the old reboot still works on the new kernel. :-) John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org