From owner-freebsd-stable@FreeBSD.ORG  Mon Feb 25 22:34:59 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C26A716A406
	for <freebsd-stable@freebsd.org>; Mon, 25 Feb 2008 22:34:59 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 1DF9113C4E3;
	Mon, 25 Feb 2008 22:34:58 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47C34293.6020104@FreeBSD.org>
Date: Mon, 25 Feb 2008 23:34:59 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Paul Schmehl <pauls@utdallas.edu>
References: <6BAFD431BFCA7093A23CE645@utd65257.utdallas.edu>
In-Reply-To: <6BAFD431BFCA7093A23CE645@utd65257.utdallas.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: 7.0 RC3 and linux linprocfs
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: Mon, 25 Feb 2008 22:34:59 -0000

Paul Schmehl wrote:
> Is it no longer required to mount linprocfs in 7.0 RC3?  I noticed that 
> it wasn't added to /etc/rc.conf, and that linux.ko is loaded.  Just 
> wondering if the mount is still required or not?
> 

linux.ko doesn't provide linprocfs.  There have not been changes to the 
linuxulator and related code recently in the release cycle.  Can you 
explain in more detail the new behaviour you are seeing?

Kris