Austin Group Minutes of the 26 August Teleconference Austin-220 Page 1 of 1 Submitted by Andrew Josey, The Open Group. August 26, 2004 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Nick Stoughton, USENIX, WG15 OR Mark Brown, IBM, TOG OR Dave Butenhof, HP Apologies Ulrich Drepper, Red Hat Joanna Farley, Sun Defect Report Processing ------------------------- The group picked up on the latest batch of defect reports, which are available at the following URL: http://www.opengroup.org/austin/aardvark/latest/ We revisited the following item from last week which had had some followup discussion on the list: XCU ERN 31 cp wording unclear OPEN Don proposed the following response, which we will review at the next meeting: 1. The Page and Line numbers referenced (relative to draft 7) should be changed as follows (all using the 2004 edition as a reference): Page: 2470 should be changed to Page: 269 Line: 10391 should be changed to Line: 10511 2. The references to lines 10316-10317 and lines 10391-10392 in the Problem statement should be changed to page 267, lines 10433-10434 and page 269, lines 10511-10512 respectively. 3. The submitter (alex.neyman@auriga.ru) states that he has no access to more recent versions of the standard [than draft 7], but says the text appears in SUSv3. We need to let Mr. Neyman know that SUSv3 is the same standard as IEEE Std 1003.1 and the ISO/IEC 9945 family of standards. 4. P267-268, L10430-10446 (including the text Mr. Neyman referenced) specify how source_file is to be interpreted when it refers to a symbolic link. The references to source_file on P268-269, L10447-10514, therefore will treat source_file as a symbolic link only if the -H option is in effect and source_file was specified as a source_file operand on the command line; or if the -P option is in effect. 5. Therefore, I believe the standard is correct as it stands and no change is required. XCU ERN 30 tr -c OPEN leave open , since we need to come up with a better example (Mark Brown) XCU ERN 27 ln -f a b is required to remove b even if the underlying link() fails Accept as marked below Add to the rationale, new para before line 21247 The Consequence of Errors section does not require "ln -f a b" to remove "b" if a subsequent link operation would fail. XBD ERN 16 Utilities that have extensions violating the Utility Syntax Guidelines Accept as marked. It was agreed that an interpretation be made , that the standard is clear and no change is required. The standard permits implementations to have extensions that violate the Utility Syntax Guidelines so long as when the utility is used in line with the forms defined by the standard that it follows the Utility Syntax Guidelines. Thus head -42 file and ls --help are permitted as extensions. Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. There are a number of open action items outstanding: 1. Don Cragun Pathname Resolution proposal 2. Larry Dwyer system() and threads 3. Joerg Schilling wording for XCU ERN 1 pax The next teleconference call is scheduled for Sep 2 2004