From owner-freebsd-standards Mon Jul 22 13:42: 4 2002 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3138C37B400; Mon, 22 Jul 2002 13:41:57 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id E566243E5E; Mon, 22 Jul 2002 13:41:55 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: from bremen.shuttle.de (localhost [127.0.0.1]) by bremen.shuttle.de (Postfix) with ESMTP id 1AE3F17D4F; Mon, 22 Jul 2002 22:41:54 +0200 (CEST) Received: (from uucp@localhost) by bremen.shuttle.de (8.12.3/8.12.3/Debian -4) with UUCP id g6MKfrG3022809; Mon, 22 Jul 2002 22:41:53 +0200 Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) by hal9000.schweikhardt.net (8.12.5/8.12.5) with ESMTP id g6MKO6Eu020503; Mon, 22 Jul 2002 22:24:06 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.12.5/8.12.3/Submit) id g6MKO5r5020502; Mon, 22 Jul 2002 22:24:05 +0200 (CEST) Date: Mon, 22 Jul 2002 22:24:05 +0200 From: Jens Schweikhardt To: Johan Karlsson Cc: standards@freebsd.org Subject: Re: add option '-t tty' to biff(1)/mesg(1) Message-ID: <20020722222405.A8193@schweikhardt.net> References: <20020722201541.B23363@numeri.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020722201541.B23363@numeri.campus.luth.se> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Johan, On Mon, Jul 22, 2002 at 08:15:41PM +0200, Johan Karlsson wrote: # Hi # # I'm planing to add an option '-t tty' to # biff and mesg. See PRs 13072/13073 for details. # # I would like to know if this will violate any # of the standards we are trying to conform to. In general, adding options is okay with respect to standards conformance. In fact, new options are a significant part of the added value of a conforming system. If POSIX forbade additional options, any vendor's system would look alike, and you - as a customer - would go for the cheapest (hm, FreeBSD comes to mind, not so bad an idea :-) # mesg(1) is covered by POSIX according to # http://people.FreeBSD.org/~schweikh/posix-utilities.html # but there is no -t option. As long as the options don't conflict and there is consensus about the usefulness you are okay. Note that the options on this page are only the POSIX mandated ones -- FreeBSD may already have more than those. # biff(1) does not seem to be in POSIX. # # Is there any other such nice summary for other # standards that I can look at? # # Unless I get good reason not to I will propose # this addition of -t on -arch the comming days. Go ahead. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message