From owner-freebsd-arch@FreeBSD.ORG Wed Jun 9 14:58:31 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C062916A4CE for ; Wed, 9 Jun 2004 14:58:31 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72EDF43D58 for ; Wed, 9 Jun 2004 14:58:31 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i59EvPls006911; Wed, 9 Jun 2004 10:57:25 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i59EvPh4006908; Wed, 9 Jun 2004 10:57:25 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 9 Jun 2004 10:57:24 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <53993.1086779790@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: arch@freebsd.org Subject: Re: dev_t / udev_t confusion ? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2004 14:58:31 -0000 On Wed, 9 Jun 2004, Poul-Henning Kamp wrote: > Personally I don't think there is much need for a long discussion and I > would prefer to see simply a show of hands for yes and no, and any hear > any really heavy duty arguments pro et contra. Sounds good to me -- I ran into this recently with the audit implementation because Solaris embeds a "udev_t" in the BSM audit format. Since the format is handled by the kernel as well as user space, I had to do the usual gymnastics to work around the udev_t confusion. I'd love to see that resolved, thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research