From owner-freebsd-hackers@FreeBSD.ORG Wed May 4 21:24:37 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17CC616A4CE for ; Wed, 4 May 2005 21:24:37 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75B0443D7F for ; Wed, 4 May 2005 21:24:36 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j44LNOiR003643; Wed, 4 May 2005 15:23:24 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 04 May 2005 15:23:24 -0600 (MDT) Message-Id: <20050504.152324.41637276.imp@bsdimp.com> To: Thomas.Sparrevohn@btinternet.com From: Warner Losh In-Reply-To: <200505042215.26426.Thomas.Sparrevohn@btinternet.com> References: <20050503222512.GA53874@crow.addict.de> <20050503.233855.116351361.imp@bsdimp.com> <200505042215.26426.Thomas.Sparrevohn@btinternet.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: mergemaster improvement (auto-update for not modified files) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 21:24:37 -0000 > On Wednesday 04 May 2005 06:38, M. Warner Losh wrote: > > > > The technical reasons are very simple. If a new system call is > > created, and programs use that new system call, then if you do an > > installworld before you boot the kernel, that can result in binaries > > not working. This has happened with important ones like /bin/sh in > > the past. In addition, if you aren't running single user, many > > different races exist in the installation process that can result in > > bad behavior. There are also potential problems with symbols in > > there's a large jump between the revisions being updated. > > > > Usually you can get away with it, but if you want to be safe, you must > > do the install in single user. Usually, however, has lead in the past > > to problems, which is why the project recommendations are > > conservative. > > > > A auto-scripted install directly run from rc.d in single-user mode would cover > both requirements - I seem to recall that Solaris had something like it at a > point. Somewhat along the lines of nextboot would be nice. How do you know where to get the sources from? What environment to build them from? However, if you could cover those issues, I'd love to see a script to deal. Maybe you could implement something that would be robust enough for the project to recommend... Warner