From owner-freebsd-current@FreeBSD.ORG Tue May 22 19:16:19 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F313016A46C; Tue, 22 May 2007 19:16:18 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id DFB4613C465; Tue, 22 May 2007 19:16:18 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7FD731A3C19; Tue, 22 May 2007 12:17:18 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0B486513AD; Tue, 22 May 2007 15:16:17 -0400 (EDT) Date: Tue, 22 May 2007 15:16:17 -0400 From: Kris Kennaway To: ports@freebsd.org, current@freebsd.org Message-ID: <20070522191617.GA77470@xor.obsecurity.org> References: <6eb82e0705211928q29881391k4da2e1a738af800d@mail.gmail.com> <4652579B.4080209@delphij.net> <6eb82e0705211954y7db95e87mdda62228e31ea013@mail.gmail.com> <20070522043637.GA65742@bsdcrew.de> <20070522072115.GC59910@xor.obsecurity.org> <20070522072545.GQ71905@droso.net> <20070522090136.C28D850BEB@unixfreunde.net> <867ir1yxv8.fsf@dwp.des.no> <20070522101643.GO71905@droso.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070522101643.GO71905@droso.net> User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: tinderbox and bad system call X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 22 May 2007 19:16:19 -0000 On Tue, May 22, 2007 at 12:16:43PM +0200, Erwin Lansing wrote: > On Tue, May 22, 2007 at 12:08:11PM +0200, Dag-Erling Smrgrav wrote: > > Martin Wilke writes: > > > Erwin Lansing writes: > > > > Another reason for to run -CURRENT and eat some more dogfood :-) > > > i think that's a wrong way to say all users and maintainer you > > > should update to current for correct building now. I'm not really > > > willing to update my miwibox to current. > > > > So don't run CURRENT in your chroot. > > > > We (mostly) support running old userlands on new kernels, but we have > > never supported running new userlands on old kernels. > > > Which is exactly what the ports tinderbox does, different userlands on a > shared kernel. Tinderboxes have always had to cope with this (in the past that mostly just affected me). Sometimes when a new CURRENT is forked you can get away with running the previous version for a while longer because the kernel ABI usually only diverges slowly. Eventually there is always an incompatible change and tinderbox machines must be upgraded to run CURRENT. This is just the price of progress. As a bonus, you get to help with QA of FreeBSD-CURRENT, which you'll be thankful for in the long run since you'll be using that branch sooner or later no matter what you do. Kris