From owner-freebsd-commit Fri Sep 29 14:25:08 1995 Return-Path: owner-commit Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA03580 for freebsd-commit-outgoing; Fri, 29 Sep 1995 14:25:08 -0700 Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA03567 for cvs-all-outgoing; Fri, 29 Sep 1995 14:25:05 -0700 Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA03550 for cvs-sbin-outgoing; Fri, 29 Sep 1995 14:25:01 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA03526 ; Fri, 29 Sep 1995 14:24:53 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA00787; Fri, 29 Sep 1995 14:24:10 -0700 From: "Rodney W. Grimes" Message-Id: <199509292124.OAA00787@GndRsh.aac.dev.com> Subject: Re: cvs commit: src/sbin Makefile To: mark@grondar.za (Mark Murray) Date: Fri, 29 Sep 1995 14:24:09 -0700 (PDT) Cc: wollman@lcs.mit.edu, mark@grondar.za, gibbs@freefall.freebsd.org, ache@freefall.freebsd.org, CVS-commiters@freefall.freebsd.org, cvs-sbin@freefall.freebsd.org In-Reply-To: <199509292034.WAA22635@grumble.grondar.za> from "Mark Murray" at Sep 29, 95 10:34:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1774 Sender: owner-commit@FreeBSD.org Precedence: bulk > > > < said: > > > > > Right now we have two wrongs making a right. We _have_ to have a make > > > with no MAKE_EBONES to make the clean distribution, followed by a nasty > > > hack to make the tainted distribution. Why can we not have "make > > > distribution" do it properly the first time? Sure we will need to fix > > > the make files, but that can of worms has been brewing for a while... > > > > Not everyone's build environment is based on `make release' and `make > > distribute'. > > Granted. Then the logic should be "if the eBones directory exists, build > eBones _unless_ asked not to", rather than "the directory must be present > _and_ permission must be granted to build eBones". > > This would mean that secure and eBones can be added to the system just > by dropping them in. At this point in this conversation I would suggest to go read the FreeBSD mail archives for similial discussions and the rational that was used when makeing the decision for that state of the defaults. It has something to do with the path of least surprize to protect people from ``unknowingling'' building a set of binaries that could not be exported. You will find almost _all_ software that has these types of restrictions in it requires 2 things to be done, the addition of the non exportable code source files and the turning of a knob to enable it. I would also suggest that the ad hoc, without white paper, and review changing of the FreeBSD source tree in this area just stinks. Insignificant discussion before action has again occured :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD