From owner-freebsd-current  Tue Mar  7  9:44:40 2000
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id BCD5B37BBFC
	for <freebsd-current@FreeBSD.ORG>; Tue,  7 Mar 2000 09:44:37 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA92455;
	Tue, 7 Mar 2000 09:42:17 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: "Matthew N. Dodd" <winter@jurai.net>
Cc: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>,
	freebsd-current@FreeBSD.ORG
Subject: Re: ssh strangeness in -current... 
In-reply-to: Your message of "Sun, 05 Mar 2000 19:57:52 EST."
             <Pine.BSF.4.21.0003051956060.690-100000@sasami.jurai.net> 
Date: Tue, 07 Mar 2000 09:42:16 -0800
Message-ID: <92448.952450936@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I keep asking myself this question; a default sysinstall package would
> give us the same end result.
> 
> I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with
> breakage.

Would you guys quit spreading FUD and start actually giving us some
DETAILS on this alleged breakage?  You've been ridiculously silent on
an issue which has been actively worked on and discussed for the last
few weeks to come forward at this late stage and start waving your
arms around.  This entire thread has been content-free so far.

- Jordan


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