From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 03:00:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5934748A for ; Wed, 9 Oct 2013 03:00:55 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id 1B66523E0 for ; Wed, 9 Oct 2013 03:00:54 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:15722] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 44/C1-16944-5E6C4525; Wed, 09 Oct 2013 03:00:53 +0000 Date: Wed, 09 Oct 2013 03:00:53 +0000 Message-ID: <44.C1.16944.5E6C4525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: Unable to installworld after successful buildworld and buildkernel References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-Mailman-Approved-At: Wed, 09 Oct 2013 04:22:37 +0000 Cc: Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 09 Oct 2013 03:00:55 -0000 > > But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING file needs to be updated for installing FreeBSD on a partition where there is no OS installed. > It's documented in Makefile.inc1 where the less commonly used options > are documented. It should be documented in the Handbook along with the > process of cross installation and image creation. > I disagree that UPDATING should document the process of installing to > other locations. That would be a distraction from it's purpose of > letting users update their systems. It's already far too complicated. -- Brooks UPDATING file has a section on cross-installing current into a separate partition. This part ought to be complete, including DB_FROM_SRC, rather than leaving a user lost at sea when a new user (unbound) sneaks in. UPDATING documented when user auditdistd was added, so why not for unbound? Tom