From owner-freebsd-current  Mon Jan 22 11:20: 8 2001
Delivered-To: freebsd-current@freebsd.org
Received: from harmony.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP id 5A34637B404
	for <current@FreeBSD.ORG>; Mon, 22 Jan 2001 11:19:51 -0800 (PST)
Received: from harmony.village.org (localhost.village.org [127.0.0.1])
	by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0MJJU911542;
	Mon, 22 Jan 2001 12:19:30 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Message-Id: <200101221919.f0MJJU911542@harmony.village.org>
To: Alfred Perlstein <bright@wintelcom.net>
Subject: Re: current panics in mount(2) 
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
	Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 22 Jan 2001 10:54:04 PST."
		<20010122105404.F7240@fw.wintelcom.net> 
References: <20010122105404.F7240@fw.wintelcom.net>  <Pine.BSF.4.21.0101230059070.29544-100000@besplex.bde.org> <200101221827.NAA40361@khavrinen.lcs.mit.edu> 
Date: Mon, 22 Jan 2001 12:19:30 -0700
From: Warner Losh <imp@harmony.village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20010122105404.F7240@fw.wintelcom.net> Alfred Perlstein writes:
: I looked at fixing this once, but got scared off because of binary
: compatibility issues.  Would 'fixing' mount to use cmsgcred be
: acceptable?

I think so.  Right now we have lots of killer, panic inducing binary
incompatibilities.  One more that doesn't suffer from the panic
inducing part would be an excellent idea.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message