From owner-freebsd-questions@FreeBSD.ORG Tue Nov 20 18:43:03 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91F245D5 for ; Tue, 20 Nov 2012 18:43:03 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 447C98FC1A for ; Tue, 20 Nov 2012 18:43:02 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Tasmi-00014h-OJ for freebsd-questions@freebsd.org; Tue, 20 Nov 2012 19:43:04 +0100 Received: from 79-139-19-75.prenet.pl ([79.139.19.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 20 Nov 2012 19:43:00 +0100 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 20 Nov 2012 19:43:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb Subject: Re: portsnap Date: Tue, 20 Nov 2012 18:42:37 +0000 (UTC) Lines: 47 Message-ID: References: <201211201826.qAKIQq8C097714@mail.r-bonomi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; FreeBSD i386; rv:16.0) Gecko/20100101 Firefox/16.0) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 18:43:03 -0000 Robert Bonomi mail.r-bonomi.com> writes: > ... > > > the authors of the portsnap docs (and the _numerous_ other applications > > > that describe the use of certain keywords used as input to that > > > appication ARE correct -- despite your boneheaded denial of that fact. Yes, it is a keyword, a keyword parameter that tells CLI command what to do (yes, a keyword that may be taken verbatim or translated into an internal command parameter(s), a keyword that represents an action). But, it is not a command, or parameter of type command. > > With regard to definition of "a command" as we practice and argue about > > here: > > > > In general (see bash(1), SHELL GRAMMAR, Simple Commands), a command is an > > executable preceded by optional vars and followed by optional parameters. > You lie. A "command" does not have to have the attributes of a command-line > invocation. Well, a second nature ... But, it is an honor :-) To drive the point: let's assume that it is a valid syntax to pass a parameter like this: "ls -al" or much better, command="", like this: command="ls -al" then it would be clear that a command (parameter) is passed to CLI command. This kind of command parameter passing fulfilles the definition of a command as referenced. If you are familiar with C function system(), you will have easier time to understand: http://www.cplusplus.com/reference/clibrary/cstdlib/system/ The prototype is: int system ( const char * command ); The command "ls -al" (yes, it is a command as referenced) is a parameter to system() function: system("ls -al"); It just says, execute that command "ls -al" in the existing execution environment. The reason I go so by the book about it is that "words have meaning" and definitions :-) jb