From owner-freebsd-geom@FreeBSD.ORG Tue Mar 6 15:53:46 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCC2E16A40A for ; Tue, 6 Mar 2007 15:53:46 +0000 (UTC) (envelope-from db@nipsi.de) Received: from mx.meta-spinner.de (mx.meta-spinner.de [213.39.242.178]) by mx1.freebsd.org (Postfix) with ESMTP id 79D2D13C48E for ; Tue, 6 Mar 2007 15:53:46 +0000 (UTC) (envelope-from db@nipsi.de) Received: from mx.meta-spinner.de (localhost [127.0.0.1]) by mx.meta-spinner.de (Postfix) with ESMTP id 52E128079A; Tue, 6 Mar 2007 16:53:45 +0100 (CET) Received: from [192.168.1.101] (unknown [192.168.1.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.meta-spinner.de (Postfix) with ESMTP id F3FA87D0BE; Tue, 6 Mar 2007 16:53:44 +0100 (CET) Message-ID: <45ED8E88.5080400@nipsi.de> Date: Tue, 06 Mar 2007 16:53:44 +0100 From: Dennis Berger User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: bug-followup@FreeBSD.org, dzs-pr@dzs.fx.org, freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: kern/104389: [geom] [patch] sys/geom/geom_dump.c doesn't encode XML entities X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2007 15:53:46 -0000 Hi, today I tried PJDs ZFS patches. After invoking zpool create I always got a coredump. After further debugging I recognized gstat isn't working either, which seems to be because of an NTFS partition with a certain name not correctly encoded as XML specification requires. Its the German "Lokaler Datenträger" which is the defaultname for drive "c". So we have to deal with those characters. I'm voting against encoding specification or something like that, but I do recommend using the escape method. For example using "&#e4;" for encoding E4 german ä and < for a "<" character. This way we can escape all illegal characters. What do you suggest? regards, -Dennis Berger