From owner-freebsd-hackers Wed Oct 8 04:58:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA13083 for hackers-outgoing; Wed, 8 Oct 1997 04:58:28 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA13074 for ; Wed, 8 Oct 1997 04:58:23 -0700 (PDT) (envelope-from aflundi@lundin.abq.nm.us) Received: from lundin.abq.nm.us. (lundin.abq.nm.us [198.59.115.228]) by kitsune.swcp.com (8.8.5/1.2.3) with ESMTP id FAA17760 for ; Wed, 8 Oct 1997 05:58:20 -0600 (MDT) Received: (from aflundi@localhost) by lundin.abq.nm.us. (8.8.7/8.8.5) id FAA01179 for hackers@FreeBSD.ORG; Wed, 8 Oct 1997 05:57:38 -0600 (MDT) Date: Wed, 8 Oct 1997 05:57:38 -0600 (MDT) From: Alan Lundin Message-Id: <199710081157.FAA01179@lundin.abq.nm.us.> In-Reply-To: asami@cs.berkeley.edu (Satoshi Asami) "Re: group assignments from make world." (Oct 7, 11:21pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: hackers@FreeBSD.ORG Subject: Re: group assignments from make world. Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 7, 11:21pm, Satoshi Asami wrote: > Subject: Re: group assignments from make world. > > * Any suggestions? Do people really want to see a "general information > > Well, for things as simple as this, maybe we can add a default > "pre-world" target or something that tests /etc against possible > outdated-ness. I agree with Satoshi, except that it could, of course, be extended beyond the bonds of /etc (/usr/include, for instance, or "what /usr/sbin/config"). If the first thing that "make world" does is run a (or a series of) pre-world test script(s), then people will know right away if it'll bomb for the things that can be tested for. Perhaps the script even could put out a message to shame people into reading the appropriate doc (saving Jordan from preforming the evil deed). For example: # make world [ blah blah ] Error: "make installworld" cannot succeed. The group "network" is not in /etc/group Read FAQ x.y and RELEASE.TXT for details. # Admittedly, automatically fixing brokenness is hard and potentially dangerous, but just checking for necessary pre-conditions ought to be fairly easy (most of the time anyway). --alan