From owner-freebsd-questions@FreeBSD.ORG Mon Mar 13 06:05:38 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A512F16A400 for ; Mon, 13 Mar 2006 06:05:38 +0000 (UTC) (envelope-from bsdlists@rfnj.org) Received: from mail.rfnj.org (ns1.rfnj.org [66.180.172.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id F415C43D49 for ; Mon, 13 Mar 2006 06:05:36 +0000 (GMT) (envelope-from bsdlists@rfnj.org) Received: by mail.rfnj.org (Postfix, from userid 58) id EF9C6872; Mon, 13 Mar 2006 01:05:35 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on rfnj.org X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=disabled version=3.1.0 Received: from localhost (localhost.rfnj.org [127.0.0.1]) by mail.rfnj.org (Postfix) with ESMTP id C4579491 for ; Mon, 13 Mar 2006 01:05:35 -0500 (EST) Received: from c-24-147-241-98.hsd1.nh.comcast.net (c-24-147-241-98.hsd1.nh.comcast.net [24.147.241.98]) by www.rfnj.org (Horde MIME library) with HTTP; Mon, 13 Mar 2006 01:05:35 -0500 Message-ID: <20060313010535.065fu4568oogkw88@www.rfnj.org> Date: Mon, 13 Mar 2006 01:05:35 -0500 From: Allen To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.4) Subject: make release / automated install / install.cfg woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 06:05:38 -0000 Is there some extra magic to making install.cfg work when rolling a release? I spent a fair amount of time this weekend preparing a custom release based off releng_6_0, and it works great but for one tiny detail.. After the installation is 'finished' and I reboot the system without the CD, it hangs with the bios complaining that it can't find anything to boot, which sounds suspiciously like the MBR wasn't written out correctly. The disk part of my install.cfg says: ===== disk=da0 bootManager=boot partition=all diskPartitionEditor da0s1-1=ufs 524288 / da0s1-2=swap 2097152 none da0s1-3=ufs 524288 /var da0s1-4=ufs 524288 /tmp da0s1-5=ufs 0 /usr 1 diskLabelEditor ===== The disk itself is setup absolutely correctly, the partitions are made, and the instally goes according to task up to and including the package installation... it just doesn't appear to Do The Right Thing when it comes to actually making the hdd bootable. Does this look like it should work? I've fiddled with various changes to the "bootManager" and "partition" lines, so far to no avail. Am I missing something here or should I start trying to figure out if the test system will boot off *any* hard drive? On a related note, when I make a change to this file, can I get away with something less than a new full "make release?" Is make rerelase or something else suitable when everything else is done and I'm just fiddling with this file? Thanks for any pointers. When I'm done with this I think I'm going to submit a doc patch for the 'make release' instructions. They are woefully inadequate for doing anything other than making a copy of your own release (unautomated) installations, and the example install.cfg still dates back to 4.x and jkh's laptop.. heh.