Date: Tue, 20 Nov 2012 11:02:17 -0500 (EST) From: "NetDispatcher" <phil@fieldservicemgmt.info> To: freebsd-questions@freebsd.org Subject: Dispatching software that works Message-ID: <20121120160217.607448BDFE@pmta4-1-07>
next in thread | raw e-mail | index | archive | help
In order to see your message, click on the following link: http://track.= zmd0.com/v/103/60e3e06e1f306f808d0b52348b54d22e6001c9566f551bd0 To unsubscribe click here: http://track.zmd0.com/u/103/60e3e06e1f306f808= d0b52348b54d22e6001c9566f551bd0 From owner-freebsd-questions@FreeBSD.ORG Tue Nov 20 17:13:08 2012 Return-Path: <owner-freebsd-questions@FreeBSD.ORG> 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 8D3F6B9E for <freebsd-questions@freebsd.org>; Tue, 20 Nov 2012 17:13:08 +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 39A808FC14 for <freebsd-questions@freebsd.org>; Tue, 20 Nov 2012 17:13:07 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from <freebsd-questions@m.gmane.org>) id 1TarNl-00027w-8U for freebsd-questions@freebsd.org; Tue, 20 Nov 2012 18:13:09 +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 <freebsd-questions@freebsd.org>; Tue, 20 Nov 2012 18:13:09 +0100 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <freebsd-questions@freebsd.org>; Tue, 20 Nov 2012 18:13:09 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb <jb.1234abcd@gmail.com> Subject: Re: portsnap Date: Tue, 20 Nov 2012 17:12:46 +0000 (UTC) Lines: 60 Message-ID: <loom.20121120T173108-456@post.gmane.org> References: <loom.20121120T094009-577@post.gmane.org> <201211201542.qAKFgLmh095631@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 <freebsd-questions.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 20 Nov 2012 17:13:08 -0000 Robert Bonomi <bonomi <at> mail.r-bonomi.com> writes: > ... > > http://en.wikipedia.org/wiki/Command-line_interface > > ... > > The general pattern of an OS command line interface is: prompt command > > param1 param2 param3 ... paramN > > No argument -- for _that_ meaning of the word. That, however, is not > the only valid usage or interpretation of it. > > The truth that you refuse to acknowledge is that in *many* cases, one or > more of the 'params' on the command line are commands TO THE APPlICATION > BEING INVOKED. > > A simple CLI will display a prompt, accept a "command line" typed by the > > [drivelectomy] > > So, we are discussing here things that are obvious. People who write > > technical or user manuals should have a clue of what they are writing and > > talking about (e.g. what is "a command", also called "an entry"). > > Otherwise they screw up the users and "it's a software error" sysadmins. > > 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. > > A "command" specifies, to the application to which it is directed, _what_ > (or _which_, if you prefer) operation/activity/function is to be performed. > In grammar terms it is a =verb=. > > A 'parameter'/'option'/'switch'/etc. instructs the application to which it > is directed to , _how_ to perform the particular action. It _modifies_ the > action to be performed. In grammar terms it is an =adverb=. > > This distinction has been known to, understood, and employed by those who > write/read/use technical instructions for well over THREE HUNDRED years. > (early multi-function machinery, such as a crane, could only perform one > action at a time -- e.g. traverse, adjust boom, lift; you moved one set > of controls to command the machine _which_ action to perform, and then > another set of controls to ccntrol how it is done. ... also responding to kpneal <at> pobox.com> ... 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. Look at PORTSNAP(8)'s synopsis again. The command is 'portsnap', anything else are parameters to it. If you call a parameter a command here, you imply that it has attributes of a command, which clearly does not, as referenced by me above. So, basically, it is an indicator, verbosely (but not required to be so if it were also verbosely defined in man page) describing an action parameter, e.g. extract, telling the actual 'portsnap' command what to do (yes - what to do, and not how to do it). jb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121120160217.607448BDFE>