From owner-freebsd-arch@FreeBSD.ORG Tue Mar 15 00:39:07 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E56A106566C; Tue, 15 Mar 2011 00:39:07 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65]) by mx1.freebsd.org (Postfix) with ESMTP id 261228FC15; Tue, 15 Mar 2011 00:39:06 +0000 (UTC) Received: from [172.22.30.42] (dulse.macktronics.com [209.181.253.69]) by coco.macktronics.com (Postfix) with ESMTPA id 8B8014AC40; Mon, 14 Mar 2011 19:20:10 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Dan Mack In-Reply-To: <4D7E228A.4090906@freebsd.org> Date: Mon, 14 Mar 2011 19:20:10 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <9B41C412-A8C4-48B9-AF45-182E5658A238@macktronics.com> References: <4D7E228A.4090906@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.1082) Cc: freebsd-current Current , freebsd-sysinstall@freebsd.org, FreeBSD Arch Subject: Re: HEADS UP: sysinstall is no longer the default installer X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2011 00:39:07 -0000 On Mar 14, 2011, at 9:13 AM, Nathan Whitehorn wrote: > I just committed (r219641) changes that make the release = infrastructure (src/release/Makefile) use bsdinstall by default instead = of sysinstall on install media. A big thank you is in order to everyone = who provided advice, criticism, and testing for this project over the = last few months! >=20 > Along with sysinstall, the original sysinstall build stuff has been = preserved (now /usr/src/release/Makefile.sysinstall) and will continue = to be for the lifetime of the 9.x release series, although it will not = be used by default. This change modifies the process of building = releases somewhat, so I'll outline changes that people who run snapshot = buildbots will have to make below, and some next steps planned with the = installer. >=20 > Changes to release(7) > ----------------------------- >=20 > Release builds work and look slightly different now, so everyone who = snapshot tinderboxes will likely find them breaking shortly. The nearest = analog to the old make release (with version-control checkouts and a = chroot) is src/release/generate-release.sh, which can be run as = generate-release.sh head /path/to/chroot/dir. If you want to include = ports and documentation on the release media, CVSUP_HOST must be defined = in the environment to point to a cvsup mirror. The output is placed in = /R in the chroot directory, as before. >=20 > If the chroot is unimportant (it ensures a total clean-room build, but = may not be necessary in most cases), you can get a release build using = the regular makefile, like so: > cd /usr/src > make buildworld buildkernel > cd /usr/src/release > make obj release >=20 >=20 >=20 Thanks! For what it's worth, I built a new release using this new = method and the only problem I ran into was getting dropped to the = "mountroot>" because the memstick's root partition failed to mount. I = am not sure if this has anything to do with your changes or not but I = thought I would bring it up. After mounting my usb stick with : = ufs:/dev/da0a it booted into bsdinstall without issue. I don't know if = this was do to kern.cam.boot_delay not being long enough or if it was a = problem with the creation of the memstick image.=20 During bsdinstall, there were a bunch of console debug messages spewing = alongside the bsdinstall text but they cleared before I could take a = picture.=20 Now we just need a ZFS template for the partition tool :-) Thanks again! Dan -- Dan Mack mack@macktronics.com