From owner-freebsd-current@FreeBSD.ORG Thu Jun 9 14:02:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 4124C16A41C for ; Thu, 9 Jun 2005 14:02:30 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECC6743D49 for ; Thu, 9 Jun 2005 14:02:29 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DgNc5-0001jg-Jd; Thu, 09 Jun 2005 14:02:29 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1DgNbv-0005xm-TF; Thu, 09 Jun 2005 07:02:20 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17064.19435.300416.290741@roam.psg.com> Date: Thu, 9 Jun 2005 07:02:19 -0700 To: Rainer Duffner References: <17063.34823.866303.74727@roam.psg.com> <42A7F87B.5000308@ultra-secure.de> <17064.16302.164797.404595@roam.psg.com> <42A84AC1.5090804@ultra-secure.de> Cc: FreeBSD Current Subject: Re: problem with boot0cfg on a twe? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 09 Jun 2005 14:02:30 -0000 > I looked in my archives (well, it's actually at gmane): > > I got this from Doug White: > >> This is a erroneous message. The actual problem is: >>> >>> 484 boot0cfg NAMI "/dev/twed0" >>> 484 boot0cfg RET open -1 errno 1 Operation not permitted >>> >>> This is a known problem with certain MBR layouts. To work around this >>> problem, set: >>> >>> sysctl kern.geom.debugflags=16 >>> then try your boot0cfg. There's a protection mechanism that sometimes gets >>> confused by certain partition table layouts. Flag 16 disables that >>> protection. I don't recommend running this unless you are explicitly >>> trying to updating something in a partition table-like area; its very easy >>> to destroy your system with the flag set! > Can you try this? bingo!!! # sysctl kern.geom.debugflags=16 kern.geom.debugflags: 0 -> 16 # boot0cfg -B -d 1 -s 1 -v twed0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63 72292437 version=1.0 drive=0x1 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) now the remaining issue is how to install a boot which goes to serial only if no crt/kbd installed. randy