Document Number: AUSTIN/119 Title: XCU/ft/2 Aardvark Change Request Report Revision Date: 2002-06-26 Source: Andrew Josey, Chair Action: for review This report contains the draft dispositions of the aardvark comments submitted against the XCU/ft/2 (2nd batch of FT aardvark) text. Aardvark Summary Table ______________________ ERN 1 Accept ERN 2 Accept ERN 3 Accept ERN 4 Accept as marked ERN 5 Accept ERN 6 Accept ERN 7 Accept ERN 8 OPEN ERN 9 OPEN ERN 10 Accept ERN 11 Accept ERN 12 Accept ERN 13 Accept ERN 14 OPEN ERN 15 OPEN ERN 16 Accept ERN 17 Accept ERN 18 Accept _____________________________________________________________________________ COMMENT Enhancement Request Number 1 bjh21@netbsd.org Defect in XCU (rdvk# 2) {bjh21:export =word} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 79 Line: 3061 Section: export Problem: The SYNOPSIS for export includes: export name[=word]... but the meaning of the optional "=word" is never explained in the text. The same problem exists with readonly. Action: Here and at page 81 line 3135 section readonly comment add to the end of the first paragraph of the description: If the name of a variable is followed by =word, the value of that variable shall be set to word. [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 2 bjh21@netbsd.org Defect in XCU (rdvk# 3) {bjh21:trap rationale} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 90 Line: 2467 Section: trap Problem: The square brackets are in the typeface used for literal text, but they're intended as metacharacters to indicate optional arguments Action: Change the square brackets to be in the typeface used for "Optional Items in Utility Syntax". [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 3 bjh21@netbsd.org Defect in XCU times (rdvk# 12) {bjh21:times mood} Tue, 28 May 2002 16:54:38 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 93 Line: 3545-3546 Section: times Problem: The first sentence of the description is phrased in the imperative rather than the indicative mood. This doesn't match the rest of the document. Action: Replace "Write" with "The times utility shall write". [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ COMMENT Enhancement Request Number 4 bjh21@netbsd.org Defect in XCU (rdvk# 4) {bjh21:ar -abi} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_____ Accept as marked below_X___ Duplicate_____ Reject_____ Rationale for rejected or partial changes: See Ed recommendation _____________________________________________________________________________ Page: 134 Line: 5023,5028 Section: ar Problem: In the SYNOPSIS for ar, the -a, -b and -i options and the posnmame operand are shown as being independent. The text describing them, at lines 5057, 5058, 5065-5066 and 5116-5117, though, indictes that the options are mutually exclusive (since a new member of the archive can't be placed both before and after the same existing member) and that posname is required if any of these options is specified. Since the syntax of the ar command is otherwise ambiguous, I think it's also reasonable to state that the posname operand is forbidden if none of these options is provided. I believe the only way to accurately express the correct syntax is by introducing two new synopses. Action: Replace line 5023 with: ar -m [-v] archive file ... ar -m -a|-b|-i [-v] posname archive file ... Both of these lines should be XSI shaded. Replace line 5028 with: ar -r [-cuv] archive file ... ar -r -a|-b|-i [-cuv] posname archive file ... The second of these lines should be XSI shaded. [Ed recommendation:Agree with the problem but a different fix is needed, see below 5023 ar -m [-v] archive file ... ar -m -a [-v] posname archive file ... ar -m -b [-v] posname archive file ... ar -m -i [-v] posname archive file ... 5028 ar -r [-cuv] archive file ... ar -r -a [-cuv] posname archive file ... ar -r -b [-cuv] posname archive file ... ar -r -i [-cuv] posname archive file ... TC1 candidate] _____________________________________________________________________________ OBJECTION Enhancement Request Number 5 joannaf@sun.com Defect in XCU c99 (rdvk# 17) {Sun-jf-dc8} Fri, 14 Jun 2002 10:35:46 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 214 Line: 8324-8339 Section: c99 Problem: Defect code : 2. Omission In the creation of the c99 utility in the Commands and Utilities volume the addition of ISO C headers and were missed from the Extended description of Standard Libraries -l c and -l m. Action: On page 214 lines 8324-8332 change: -l c This operand shall make visible all functions referenced in the System Interfaces volume of IEEE Std 1003.1-2001, with the possible exception of those functions listed as residing in , , , , , , , , , , , pthread_kill(), and pthread_sigmask() in , , functions marked as extensions other than as part of the MF or MPR extensions in , functions marked as ADV in , and functions marked as CS, CPT, and TMR in . This operand shall not be required to be present to cause a search of this library. to: to: -l c This operand shall make visible all functions referenced in the System Interfaces volume of IEEE Std 1003.1-2001, with the possible exception of those functions listed as residing in , , , , , , , , , , , , , pthread_kill(), and pthread_sigmask() in , , functions marked as extensions other than as part of the MF or MPR extensions in , functions marked as ADV in , and functions marked as CS, CPT, and TMR in . This operand shall not be required to be present to cause a search of this library. On page 214 lines 8338-8339 change: -l m This operand shall make visible all functions referenced in . An implementation may search this library in the absence of this operand. to: -l m This operand shall make visible all functions referenced in , and . An implementation may search this library in the absence of this operand. [Ed recommendation: TC1 candidate] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 6 joannaf@sun.com Defect in XCU c99 (rdvk# 16) {Sun-jf-dc7} Thu, 13 Jun 2002 10:27:38 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 215 Line: 8355 Section: c99 Problem: Defect code : 1. Error Reference of libxnet library should be libxnet.a Action: Change on page 215 lines 8355-8356: It is unspecified whether the libraries libc.a, libm.a, librt.a, libpthread.a, libl.a, liby.a, or libxnet exist as regular files. to: It is unspecified whether the libraries libc.a, libm.a, librt.a, libpthread.a, libl.a, liby.a, or libxnet.a exist as regular files [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ COMMENT Enhancement Request Number 7 bjh21@netbsd.org Defect in XCU (rdvk# 1) {bjh21:cd -LP} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 226 Line: 8736 Section: cd Problem: The SYNOPSIS for cd says: cd [-L] [-P] [directory] but -L and -P are mutually exclusive (albeit with defined priorities, but that's allowed by rule 8 of section 12.1 of XBD). They should be marked as such. This is necessary to satisfy Guideline 11 of the Utility Syntax Guidelines. Action: Replace the SYNOPSIS for cd with: cd [-L|-P] [directory] [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ OBJECTION Enhancement Request Number 8 eggert@twinsun.com Defect in XCU diff (rdvk# 11) {eggert20020514a} Tue, 14 May 2002 13:41:57 +0100 (BST) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject_____OPEN Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 320 Line: 12320 Section: diff Problem: Defect code : 1. Error POSIX specifies a behavior for 'diff -c' that does not agree with existing practice when contexts that contain zero lines or one line. Here is an example, showing current existing practice: $ touch empty $ echo hello >oneline $ /usr/bin/diff -c empty oneline *** empty Fri May 10 12:22:48 2002 --- oneline Fri May 10 12:22:58 2002 *************** *** 0 **** --- 1 ---- + hello POSIX does not allow this behavior: it requires that two line numbers must appear in each line range of output. That is, POSIX presumably would require output that looked like this instead: *** empty Fri May 10 12:22:48 2002 --- oneline Fri May 10 12:22:58 2002 *************** *** 1,0 **** --- 1,1 ---- + hello No "diff" implementations behave that way, though. Also, POSIX does not specify how to determine the line number of an empty range. Action: Change XCU page 320 lines 12320-12321 to read: Next, the range of lines in file1 shall be written in the following format if the range contains two or more lines: "*** %d,%d ****\n", , and the following format otherwise: "*** %d ****\n", The ending line number of an empty range shall be the number of the preceding line, or 0 if the range is at the start of the file. Change XCU page 321 lines 12329-12330 to read: Next, the range of lines in file2 shall be written in the following format if the range contains two or more lines: "--- %d,%d ----\n", , and the following format otherwise: "--- %d ----\n", [Ed recommendation: needs more folks to look at it to ensure we get the right fix] _____________________________________________________________________________ OBJECTION Enhancement Request Number 9 gwc@opengroup.org Defect in XCU ed (rdvk# 10) [gwc ed G] Fri, 24 May 2002 15:38:40 +0100 _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject_____OPEN Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 340 Line: 13069 Section: ed Problem: Defect code : 1. Error A problem with the description of the ed "g" command was fixed in the revision by adding the text "Any line modified by the command list shall be unmarked." The same problem also affects the "G" command, but this was not corrected. Presumably this was an oversight, not intentional. Action: After "... affect any line in the buffer.", add "Any line modified by the command shall be unmarked." [Ed recommendation: as for previous ERN] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 10 bjh21@netbsd.org Defect in XCU (rdvk# 5) {bjh21:false stderr} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 432 Line: 16698 Section: false Problem: The STDERR section contains "None.", but section 1.11 (Utility Description Defaults, p 24, ll 979-998) doesn't provide a meaning for this. Action: Replace "None." with "Not used." [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ COMMENT Enhancement Request Number 11 bjh21@netbsd.org Defect in XCU file (rdvk# 8) {bjh21:file usg} Wed, 15 May 2002 14:41:42 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 442 Line: 17041-17042 Section: file Problem: These lines claim that "file" conforms to the Utility Syntax Guidelines, but in fact lines 17056-17060 indicate that in respect of the -d, -M and -m options, it fails to comply with Guideline 11. Action: After "Utility Syntax Guidelines" insert ", except that the order of the -m, -d, and -M options shall be significant". [ This text is copied from the description of m4's -U and -D options. ] [Ed recommendation: Accept for TC1] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 12 gwc@opengroup.org Defect in XCU locale (rdvk# 15) [gwc locale stdout] Mon, 10 Jun 2002 19:38:46 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 551 Line: 21146 Section: locale Problem: Defect code : 1. Error Some extra double-quote characters have found their way onto this line. Action: Change "%s=\""%s\""\n", To "%s=\"%s\"\n", (It may be useful to compare the source for this line with that for line 21169, where the quotes are right.) [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ OBJECTION Enhancement Request Number 13 gwc@opengroup.org Defect in XCU mailx (rdvk# 13) [gwc mailx +file] Sat, 1 Jun 2002 12:51:46 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 593 Line: 22848-22852 Section: mailx Problem: Defect code : 1. Error POSIX.2 interpretation #122 identified a correction to be made in the revision, but the change has not been made (despite being listed in the mailx change history as having been addressed). Action: Replace the paragraph with the following text, which is the text suggested by the submitter of POSIX.2 interp #122 but with minor editorial changes: File names, where expected, shall be subjected to the following transformations, in sequence: If the filename begins with an unquoted plus sign, and the folder variable is defined (see the folder variable), the plus sign shall be replaced by the value of the folder variable followed by a slash. If the folder variable is unset or is set to null, the filename shall be unchanged. Shell word expansions shall be applied to the filename (see Section 2.6 (on page 36)). If more than a single pathname results from this expansion and the command is expecting one file, the effects are unspecified. [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ COMMENT Enhancement Request Number 14 gwc@opengroup.org Defect in XCU patch (rdvk# 14) [gwc patch ifdef] Fri, 7 Jun 2002 16:10:46 +0100 _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject_____OPEN Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 688 Line: 26482 Section: patch Problem: Defect code : 3. Clarification required The description of the patch -D option does not indicate which way round the ifdef selection should be. Given the file source.c and a patch to be applied to it, when patch is used as follows: patch -D DEFNAME source.c < patchfile is compiling the modified source.c *with* -D DEFNAME equivalent to compiling the original version of source.c, or is compiling the modified source.c *without* -D DEFNAME equivalent to compiling the original version of source.c? There are existing implementations of patch which differ in this respect. Action: The options would seem to be ... a. State that the behaviour is unspecified, and add a note under APPLICATION USAGE to warn application writers about it. b. Require that the ifdef selection is one way round or the other. Which way round would depend on historical behaviour and how many existing implementations do it each way. [Ed recommendation: concept appears correct but more consideration needed] _____________________________________________________________________________ OBJECTION Enhancement Request Number 15 ken.dawson@sun.com Defect in XCU pax options (rdvk# 18) {sunw-pax-01} Thu, 20 Jun 2002 23:50:22 +0100 (BST) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject_____OPEN Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 701 Line: 27030-27065 Section: pax Problem: Defect code : 1. Error The specification of the exthdr.name (and globexthdr.name) option (and default values) creates a potential race condition between two different processes extracting identically-named files from pax-format archives. The default value for exthdr.name is %d/PaxHeaders/%f and the default value for globexthdr.name is %d/GlobalHead.%n There is no way for the implemenation (or the user) to ensure that different instances of pax extracting a file named "/a/b/foo" will not collide when processing the extended header information associated with "foo". What provision can be made so that this race condition is avoided? Action: Replace the text @P701, L27042 with the following: 27042 %p The process id of the pax process. %% A '%' character. Replace the text @P701, L27046 with the following: 27046 %d/PaxHeaders.%p/%f Replace the text @P702, L27059 with the following: 27059 %p The process id of the pax process. %% A '%' character. Replace the text @P702, L27063 with the following: 27063 %d/GlobalHead.%p.%n [Ed recommendation: problem is correct,need more discussion on the fix] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 16 gwc@opengroup.org Defect in XCU stty (rdvk# 9) [gwc stty nl] Thu, 23 May 2002 17:36:14 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 887 Line: 34262 Section: stty Problem: Defect code : 1. Error POSIX.2 interpretation #133 identified an error in the description of "stty nl", but the fix has not been applied in the revision. Action: Change "Enable (disable) icrnl" to "Disable (enable) icrnl". [Ed recommendation: Accept TC1 candidate] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 17 bjh21@netbsd.org Defect in XCU (rdvk# 6) {bjh21:false stderr} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 929 Line: 35818 Section: true Problem: The STDERR section contains "None.", but section 1.11 (Utility Description Defaults, p 24, ll 979-998) doesn't provide a meaning for this. Action: Replace "None." with "Not used." [Ed recommendation: Accept for TC1] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 18 bjh21@netbsd.org Defect in XCU (rdvk# 7) {bjh21:false stderr} Mon, 13 May 2002 17:59:43 +0100 (BST) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 929 Line: 35824 Section: true Problem: The exit status of true is listed as "Default.", but section 1.11 (Utility Description Defaults, p 25, ll 1037-1052) doesn't provide a meaning for this. Action: Replace "Default." with "Zero." [Ed recommendation: Accept TC1 candidate]