From owner-freebsd-current@FreeBSD.ORG  Fri Feb  9 11:33:09 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id CBAB616A400
	for <current@freebsd.org>; Fri,  9 Feb 2007 11:33:09 +0000 (UTC)
	(envelope-from rizzo@icir.org)
Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68])
	by mx1.freebsd.org (Postfix) with ESMTP id A492713C481
	for <current@freebsd.org>; Fri,  9 Feb 2007 11:33:09 +0000 (UTC)
	(envelope-from rizzo@icir.org)
Received: from xorpc.icir.org (localhost [127.0.0.1])
	by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l19BX86l096942;
	Fri, 9 Feb 2007 03:33:08 -0800 (PST)
	(envelope-from rizzo@xorpc.icir.org)
Received: (from rizzo@localhost)
	by xorpc.icir.org (8.12.11/8.12.3/Submit) id l19BX8nH096941;
	Fri, 9 Feb 2007 03:33:08 -0800 (PST) (envelope-from rizzo)
Date: Fri, 9 Feb 2007 03:33:08 -0800
From: Luigi Rizzo <rizzo@icir.org>
To: current@freebsd.org
Message-ID: <20070209033308.A96890@xorpc.icir.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Cc: 
Subject: generic 'dev' loopback driver ?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 09 Feb 2007 11:33:09 -0000

is there anything around which implements a generic
'dev' loopback driver, i.e. something that appears
as a /dev/foo entry on one side, and transparently
passes requests (open, ioctl, read/write) suitably encoded to a
file descriptor ?

I am basically looking at the skeleton of
something like pty-ttyp or tun-/dev/tun and so on...

	cheers
	luigi