From owner-freebsd-current@FreeBSD.ORG Wed Apr 28 00:16:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A539816A4CE for ; Wed, 28 Apr 2004 00:16:51 -0700 (PDT) Received: from cl-mailhost.FernUni-Hagen.de (sycamore.fernuni-hagen.de [132.176.114.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BFF043D5C for ; Wed, 28 Apr 2004 00:16:51 -0700 (PDT) (envelope-from jfh@es-i2.FernUni-Hagen.de) Received: from es-i2.fernuni-hagen.de ([132.176.7.81]) by cl-mailhost.FernUni-Hagen.de with esmtp (Exim 4.24) id 1BIjJK-0007FQ-NN; Wed, 28 Apr 2004 09:16:50 +0200 Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (Postfix) with ESMTP id C1FA85936; Wed, 28 Apr 2004 09:16:49 +0200 (CEST) From: Fritz Heinrichmeyer To: Doug White Date: Wed, 28 Apr 2004 09:16:51 +0200 User-Agent: KMail/1.6.2 References: <200404261134.35476.fritz.heinrichmeyer@fernuni-hagen.de> <20040427102742.O34678@carver.gumbysoft.com> In-Reply-To: <20040427102742.O34678@carver.gumbysoft.com> MIME-Version: 1.0 Content-Disposition: inline X-UID: 609 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404280916.51605.fritz.heinrichmeyer@fernuni-hagen.de> cc: current@freebsd.org Subject: boot0cfg with new default under current ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 28 Apr 2004 07:16:51 -0000 Am Dienstag, 27. April 2004 19:28 schrieb Doug White: > On Mon, 26 Apr 2004, Fritz Heinrichmeyer wrote: > > recently i had no success in using boot0cfg and bsdlabel to repair boot > > process under current. The only way that worked was booting with a > > live-cd and using sysinstall from there. Is there some documentation > > regarding freebsd-current for this? > > Man pages :) I think there is a handbook section on boot0cfg too, > although I'd have to check. the line boot0cfg -m 0x5 -B -o packet ad0 || echo there were problems worked, the new mask showed that that there was actually something written and boot process was no more broken. Maybe "-o packet" is a good default these days ... -- Fritz Heinrichmeyer FernUniversitaet, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh