From owner-freebsd-security Tue Oct 19 5:37: 5 1999 Delivered-To: freebsd-security@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 3CCDB16DA4 for ; Tue, 19 Oct 1999 05:37:00 -0700 (PDT) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id IAA13922; Tue, 19 Oct 1999 08:36:17 -0400 (EDT) (envelope-from matt@zigg.com) Date: Tue, 19 Oct 1999 08:36:16 -0400 (EDT) From: Matt Behrens To: "Matthew D. Fuller" Cc: David G Andersen , Jay Nelson , Cy.Schubert@uumail.gov.bc.ca, jwyatt@rwsystems.net, glewis@trc.adelaide.edu.au, freebsd-security@FreeBSD.ORG Subject: Re: FreeSSH In-Reply-To: <19991018165725.C29597@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 Oct 1999, Matthew D. Fuller wrote: : On Sun, Oct 17, 1999 at 02:06:32PM -0400, a little birdie told me : that Matt Behrens remarked : > : > That would probably do pretty well for the initial install, but it : > unfortunately doesn't address the problem of how to stop make world : > from happily replacing all of the newly-missing components. : : This is why I stick non-stock things in /usr/local. Yes, but we're referring to now-"stock" things that will, for one reason or another, end up totally nonexistent on the system. For example, a system without any UUCP stuff would suddenly become a system *with* UUCP stuff after make world. Matt Behrens Owner/Administrator, zigg.com Chief Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message