From owner-freebsd-current Wed Sep 29 17:37:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id 285FC151F6 for ; Wed, 29 Sep 1999 17:37:29 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id 83B9F7C33; Wed, 29 Sep 1999 19:37:28 -0500 (CDT) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14322.45256.403099.72608@celery.zuhause.org> Date: Wed, 29 Sep 1999 19:37:28 -0500 (CDT) To: Ben Rosengart Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: sigset_t changes committed In-Reply-To: References: <19990929231253.B26394@foobar.franken.de> X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Rosengart writes: > On Wed, 29 Sep 1999, Harold Gutch wrote: > > > I interpreted the way of currently handling things (build the > > kernel first, then the userland) to be a _temporary_ solution, > > that Marcel was working on being fixed. If this is not the case, > > then I agree with you. > > If I understand correctly, it only needs to be done once per system, but > it makes no difference whether it happens on a given system now or six > months from now. And if I'm running a version of 3.x or older version of -current that can't even build a working kernel because config is out of sync with the kernel sources? I agree with Rod Grimes, if you can't build it with make world, and you're not going to fix it so it can be, it should be backed out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message