From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 14:29:51 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5859E16A404 for ; Sun, 24 Feb 2008 14:29:51 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 2AF8613C4EE for ; Sun, 24 Feb 2008 14:29:51 +0000 (UTC) (envelope-from atom@smasher.org) Received: (qmail 23282 invoked by uid 1000); 24 Feb 2008 05:21:41 -0000 Message-ID: <20080224052141.23275.qmail@smasher.org> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Sun, 24 Feb 2008 18:21:39 +1300 (NZDT) From: Atom Smasher In-Reply-To: <20080223131937.182373b2@bhuda.mired.org> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080223123556.3eee709d@bhuda.mired.org> <20080223.110047.-397883947.imp@bsdimp.com> <20080223131937.182373b2@bhuda.mired.org> To: freebsd-hackers@freebsd.org X-POM: The Moon is Waning Gibbous (91% of Full) X-Hashcash: 1:20:0802240521:freebsd-hackers@freebsd.org::0OIjZZ6hi+xh8yhf:000000 0000000000000000000000003K35 Subject: Re: find -lname and -ilname implemented X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2008 14:29:51 -0000 On Sat, 23 Feb 2008, Mike Meyer wrote: > The problem with this argument is that there are no limits on it, other > than the developers definition of "trivial". OS X has already carried > this argument to the point that they've replaced /bin/sh with bash. ======================= i've seen that on linux, that /bin/sh is a symlink to /bin/bash and IMHO that's just wrong. otherwise, i think there's nothing wrong with adding functionality to 'find', as long as it doesn't break anything. a bash script that starts with '#!/bin/sh' is begging to break things (i filed a kde bug report about that; there was a bash-centric script that didn't work with sh), i can't think of a case that added functionality to find would break anything. i'm especially in favor of adding "unnecessary" functionality since i've recently been working on some core-install solaris boxes... the find function doesn't support 'maxdepth', the grep has no '-A', '-B' or '-C' options... i could go on, but the security requirements don't allow us to install gnu-find, gnu-grep, etc... if it doesn't break anything and it increases compatibility, i can't think of any reason to fight it. you seem opposed to the changes to find, but haven't cited any cases where the added functionality would be a problem. if we were to draw two columns on a piece of paper and label the columns "pro" and "con", then list consequences of the added functionality to find, we'd come up with a few things for the "pro" column... but you haven't really convinced me that anything needs to be added to the "con" column, except that you think it's not needed. -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "It really depends upon how our nation conducts itself in foreign policy. If we're an arrogant nation, they'll resent us. If we're a humble nation, but strong, they'll welcome us." -- George "dubya" Bush Bush-Gore debate, 11 Oct 2000