From owner-freebsd-current@FreeBSD.ORG  Fri May 23 15:27:55 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 96EDA37B401; Fri, 23 May 2003 15:27:55 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9965743F93; Fri, 23 May 2003 15:27:52 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h4NMRmLp020811;
	Sat, 24 May 2003 00:27:49 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Daniel C. Sobral" <dcs@tcoip.com.br>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 23 May 2003 17:46:12 -0300."
             <3ECE8894.2000508@tcoip.com.br> 
Date: Sat, 24 May 2003 00:27:48 +0200
Message-ID: <20810.1053728868@critter.freebsd.dk>
cc: CURRENT <freebsd-current@freebsd.org>
cc: Robert Watson <rwatson@freebsd.org>
Subject: Re: /dev/null panic still alive 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Fri, 23 May 2003 22:27:55 -0000

In message <3ECE8894.2000508@tcoip.com.br>, "Daniel C. Sobral" writes:
>Poul-Henning Kamp wrote:
>> 
>> Somewhere, probably under /compat/linux/dev you have some device nodes
>> on a UFS filesystem.  You shouldn't need those (I think ?) and they
>> are likely the cause of this.
>
>True enough. As for needing it, tell that to linux_base. I'm an innocent 
>bystander.
>
>> Kirk's on vacation and I havn't heard back from rwatson what he think
>> we should do.
>
>He did mention he thought trustedbsd had a patch for this.

Yes, unfortunately, that patch which is also in -current does not work.

It works for VFIFO's but not for VCHR

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.