From owner-freebsd-stable@FreeBSD.ORG  Wed Apr 12 14:35:31 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CF7C816A400;
	Wed, 12 Apr 2006 14:35:31 +0000 (UTC)
	(envelope-from craig@feniz.gank.org)
Received: from ion.gank.org (ion.gank.org [69.55.238.164])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9C80943D4C;
	Wed, 12 Apr 2006 14:35:31 +0000 (GMT)
	(envelope-from craig@feniz.gank.org)
Received: by ion.gank.org (Postfix, from userid 1001)
	id B7148115B2; Wed, 12 Apr 2006 09:35:30 -0500 (CDT)
Date: Wed, 12 Apr 2006 09:35:26 -0500
From: Craig Boston <craig@feniz.gank.org>
To: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org
Message-ID: <20060412143526.GA38254@nowhere>
Mail-Followup-To: Craig Boston <craig@feniz.gank.org>,
	freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org
References: <20060409170917.GA85736@saturn.kn-bremen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060409170917.GA85736@saturn.kn-bremen.de>
User-Agent: Mutt/1.4.2.1i
Cc: 
Subject: Re: devfs weirdness with kqemu
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2006 14:35:31 -0000

On Sun, Apr 09, 2006 at 07:09:17PM +0200, Juergen Lock wrote:
>  Is this something the kld is doing wrong (/usr/ports/emulators/kqemu-kmod)
> or is it a devfs problem?  The report I got was for 6.0, but it also
> happens for me on RELENG_5.  This is nothing serious (kqemu works), but
> it certainly can be confusing for users...

Admittedly the cloning behavior for kqemu is a bit of a hack, but the
module should be working.  Quirky behavior with 'ls' is better than
limiting it to a single process IMO.

IIRC there's still some Linux-ish assumptions made by kqemu about how
devices are opened multiple times that need to be correctly fixed rather
than just worked around.  Been a while since i've looked at it though.

Craig