From owner-freebsd-chat Mon Oct 20 23:47:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23800 for chat-outgoing; Mon, 20 Oct 1997 23:47:28 -0700 (PDT) (envelope-from owner-freebsd-chat) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA23795 for ; Mon, 20 Oct 1997 23:47:25 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id IAA02083; Tue, 21 Oct 1997 08:47:28 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id IAA04464; Tue, 21 Oct 1997 08:56:43 +0200 (MEST) Message-ID: <19971021085642.49975@gil.physik.rwth-aachen.de> Date: Tue, 21 Oct 1997 08:56:42 +0200 From: Christoph Kukulies To: Wolfgang Helbig Cc: Mike Smith , kuku@gilberto.physik.RWTH-Aachen.DE, grog@lemis.com, freebsd-chat@freefall.FreeBSD.org Subject: Re: bad system call - world build References: <199710201433.AAA01025@word.smith.net.au> <199710202228.AAA27784@rvc1.informatik.ba-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [redirected to chat] In-Reply-To: <199710202228.AAA27784@rvc1.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Tue, Oct 21, 1997 at 12:28:40AM +0200 On Tue, Oct 21, 1997 at 12:28:40AM +0200, Wolfgang Helbig wrote: > > > > > ===> share/termcap > > > > > ex - /a/src/share/termcap/termcap.src < /a/src/share/termcap/reorder > /dev/null > > > > > Bad system call - core dumped > > ... > > > > This is almost a FAQ. Build a new kernel first, boot with it, then > > > > you should be able to continue. > > > > > > Not quite, Greg. Normally I know what to do when proc.h has been changed > > > (ps/w etc. weirdnesses) but in this case I'm not sure whether > > > building a new kernel (3.0-current) and booting it on top of a > > > set of (up to then) 2.2.2-binaries would be a could remedy here. > > > > Funnily enough, Greg is quite right. I almost feel that I'm insulting > > him by backing him up, but Chris, this *is* a FAQ, and if you were > > reading the -current list like you're supposed to, you would know all > > about this. > > > > You do need a newer kernel to get past this. The issue *was*announced* > > when the change was made. There was some attempt made to put in place > > code to deal with the new system call, but it appears to have been > > unsuccessful and at any rate is only needed for the bootstrapping case. > > Going from 2.x to 3.x is going to get harder, not easier. > > > > > I will more likely follow the advice of your forespeaker, namely > > > excluding the termcap subdir from the worldbuild. > > > > This is stupid, and fails to address the problem. > > Hmm. As far as I recall, we had some interface change of > mount(8) in -current about half year ago which made it > impossible to successfully mount with a new kernel and old userland > environmemt. Exactly this I meant. I ran into this trap several times. Not because I made the same mistake twice but someone deleted /kernel and /kernel.old was unusable due to the mount problem. Only fixit floppy helped at that time. Actually I didn't want to contribute to this thread anymore because it's just hot air. > > So even if this is a FAQ the answer depends... Most of the time Greg said 'almost a FAQ' and I would leave it at that. I don't know what the critical mass is to make an issue a FAQ but believe me, I sifted through my saved freebsd-current mail archive for 'system call' before asking ans didn't find nothing relevant. > building userland first gives you less trouble than building > the kernel first. Just think about outdated config(8) which is > still part of userland. > > I don't think my suggestion is that stupid. > > Wolfgang -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de