From owner-freebsd-current@FreeBSD.ORG  Wed Jul 14 05:48:42 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 43C7616A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 14 Jul 2004 05:48:42 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 39EEE43D2F
	for <freebsd-current@freebsd.org>;
	Wed, 14 Jul 2004 05:48:41 +0000 (GMT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6E5kAUn058428;
	Tue, 13 Jul 2004 23:46:11 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Tue, 13 Jul 2004 23:46:16 -0600 (MDT)
Message-Id: <20040713.234616.66794208.imp@bsdimp.com>
To: jdp@polstra.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <XFMail.20040712143801.jdp@polstra.com>
References: <200407122234.21351.dfr@nlsystems.com>
	<XFMail.20040712143801.jdp@polstra.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: kldload won't load
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Wed, 14 Jul 2004 05:48:42 -0000

In message: <XFMail.20040712143801.jdp@polstra.com>
            John Polstra <jdp@polstra.com> writes:
: On 12-Jul-2004 Doug Rabson wrote:
: > Hmm. Maybe the simplest thing would be to print the link errors using 
: > uprintf() instead of printf().
: 
: That's a good idea.  It would be a lot better than what we have now.

So long as we fix uprintf to not fail when there's not controlling
tty.  Right now that's a good way to panic a system.

Warner