From owner-freebsd-current Mon Jul 17 01:54:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA15383 for current-outgoing; Mon, 17 Jul 1995 01:54:09 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA15376 for ; Mon, 17 Jul 1995 01:54:06 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id BAA00976; Mon, 17 Jul 1995 01:54:13 -0700 From: "Rodney W. Grimes" Message-Id: <199507170854.BAA00976@gndrsh.aac.dev.com> Subject: Re: Move mt(1) to /bin? To: mpp@legarto.minn.net (Mike Pritchard) Date: Mon, 17 Jul 1995 01:54:12 -0700 (PDT) Cc: bde@zeta.org.au, freebsd-current@freebsd.org In-Reply-To: <199507170842.DAA03545@mpp> from "Mike Pritchard" at Jul 17, 95 03:42:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2227 Sender: current-owner@freebsd.org Precedence: bulk > > Rodney W. Grimes wrote: > >... > > ever it is to force it to be a static binary. But it still does not > > answer the long term question of exactly what criteria says things go > > in /bin vs /usr/bin. Nor does it get on with analyzing this problem > > so, or coming up with a solution that prevents this type of discussion > > from reoccur-ing. > > Is there any reason not to decide this stuff right now (or at least > before 2.2)? How about everyone compiles a list of binaries they feel > should reside in /bin or /sbin and make an argument for them. > After 2 - 3 weeks, the list of proposed moves can be submitted to > the core team along with the pro/con arguments for each binary in question. Before you make decisions you should create formal criteria for the reasons things belong where they belong. If you use the above mechanism you may very well get folks like me or Bruce who find the distinction between /bin and /usr/bin of static vs shared to be pretty meaningless any more and just say ``mv /usr/bin/* /bin; mv /usr/sbin/* /sbin''. ``binaries they feel should reside'' is to wide open, we must have a list of reasonable things that when you take some binary and run down this list it clearly says one place or the other. > I'm willing to collect the data and submit a proposal to the core > team based on that data if that is what is needed. > > Let me know. If we want to pursue this, I'll draft something > up to send out to the mailing lists requesting the required > information, and we might consider posting it to the USENET groups. No! Don't do that, that is design by committee and you only end up with a mess when you do that. > Even if we decide that nothing moves locations, we may find > a set of binaries that are *REALLY* useful in getting a broken > system back up and running that could serve as an auxiliary floppy > to the boot and root floppies in emergency situations. 15 years of unix experience tell me what that list is already... and it is not the same for any 2 sites... though there is a common subset. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD