From owner-freebsd-current@FreeBSD.ORG  Sat May 10 03:25:57 2003
Return-Path: <owner-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 1CE2637B401
	for <freebsd-current@freebsd.org>;
	Sat, 10 May 2003 03:25:57 -0700 (PDT)
Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 47EF243FE9
	for <freebsd-current@freebsd.org>;
	Sat, 10 May 2003 03:25:56 -0700 (PDT)	(envelope-from msch@snafu.de)
Received: from tc01-n70-118.de.inter.net ([213.73.70.118])
	by smart.eusc.inter.net with esmtp (Exim 3.36 #4)
	id 19ERYA-00017B-00; Sat, 10 May 2003 12:25:54 +0200
From: Matthias Schuendehuette <msch@snafu.de>
Organization: Micro$oft-free Zone
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Date: Sat, 10 May 2003 12:25:53 +0200
User-Agent: KMail/1.5.1
References: <13473.1052511292@critter.freebsd.dk>
In-Reply-To: <13473.1052511292@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305101225.53877.msch@snafu.de>
cc: freebsd-current@freebsd.org
Subject: Re: GEOM loose end?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: msch@snafu.de
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 10 May 2003 10:25:57 -0000

Hello phk,

On Friday 09 May 2003 22:14, Poul-Henning Kamp wrote:
> [...]
> The very reason why you need to set a debug flag in geom is that
> libdisk sneaks under the entire GEOM stack when it writes its changes
> to the disk, and the kernel/GEOM has not been and will not be bloated
> with code to detect this hack.
> [...]
> Unfortunately, I don't have time to work much on this issue, just
> getting the kernel side and the basic tools (bsdlabel(8), sunlabel(8)
> etc in shape takes most of the time I have.

Perhaps a side issue - is it possible to tell the GRUB-people how to 
deal with GEOM correctly?

Sure, the 'kern.geom.debugflags=16'-setting seems to be a workaround (?) 
but not a solution.
-- 
Ciao/BSD - Matthias

Matthias Schuendehuette	<msch [at] snafu.de>, Berlin (Germany)
Powered by FreeBSD 5.0-CURRENT