Austin Group Minutes of the 14 April Teleconference Austin-253 Page 1 of 1 Submitted by Andrew Josey, The Open Group. April 15, 2005 Attendees Andrew Josey, The Open Group Mats Wichmann Nick Stoughton, USENIX, ISO/IEC OR Don Cragun , Sun, PASC OR Mark Brown, IBM, TOG OR Ulrich Drepper, Red Hat We also had an IRC channel open for this call irc://irc.freestandards.org/austin Action item review --------------------- Just the updates on Austin/240r1 are noted here. ACTION AI-2005-01-09 Andrew Josey & Mats Wichmann to propose a time and place for a joint Austin group/LSB Workgroup meeting to consider LSB/POSIX conflicts, to be held as soon as conveniently possible. Status: OPEN Andrew has updated the report for 3.0-preview1 LSB 3.0-Preview2 is due Friday April 15 and expected to have a one week review. Nick still has an action to prepare an agenda for a teleconference. ACTION AI-2005-01-06: AJ to contact Jack McCann at HP for views on getnameinfo document, and for any other networking issues that may concern us. Status: OPEN, looking for a volunteer to acts as a liaison to the networking folks at IETF Nick reported that he might have some possible candidates. 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/ XSH ERN 88 rename Reject The decision to reject this item was not changed, but we did discuss the further mail that Jim Meyering raised on this topic on April 1. https://www.opengroup.org/sophocles/show_mail.tpl?source=L&listname=austin-review-l&id=1917 This proposed an alternative approach regarding marking the current behavior as obsolescent. There were still concerns voiced about changing the semantics of the rename() function. One suggestion was that a change that could find more consensus would be confined to the mv utility only. XBD ERN 53 OPEN Mark had developed a proposal http://www.opengroup.org/austin/mailarchives/austin-group-l/msg08294.html (see aardvark). Nick reported that the C committee was sympathetic to the approach being proposed and would entertain a defect report. P J Plauger would be able to join the teleconference on approach to solving this matter without changes and could join the next teleconference. There was some concern over the naming of the variable. An alternate proposal is: __POSIX_CHAR_NOCAST_WCHAR__ Also XSI shaded text needs to be added: On XSI-conformant systems the variable __POSIX_CHAR_NOCAST_WCHAR__ shall not be defined by the implementation. It was also noted for the record that the current requirements in the existing standard are not incompatible with the C standard they are just a restricted set. XBD ERN 54 ENOTSUP and ENOPNOTSUP distinct values Accept as marked below It was agreed that the item be forwarded down the interpretations track. "The standard is clear, and conforming implementations must provide these symbols with distinct values. Concerns have been raised and are being forwarded to the sponsor." Notes to the Editor for a future revision (not part of the interpretation) On p 221, line 7777, change [ENOTSUP] Not supported. to [ENOTSUP] Not supported (may be the same value as [EOPNOTSUPP]). and at line 7780, change [EOPNOTSUPP] Operation not supported on socket. to [EOPNOTSUPP] Operation not supported on socket (may be the same value as [ENOTSUP]). XBD ERN 55 restrict parameters on pthread_mutex_timedlock in pthread.h Accept XCU ERN 51 mv file hierarchy duplication Accept as marked below The wording had been proposed at a previous meeting and was now accepted. We believe that the standard being silent allows either behavior. We agreed to state it explicitly. Add to mv DESCRIPTION Page 656 before 25426 Insert into p656 before the existing para that states: "If the duplication of the file hierarchy fails for any reason, mv shall write a diagnostic message to standard error, do nothing more with the current source_file, and go on to any remaining source_files." If files being duplicated to another filesystem have hard links to other files it is unspecified whether the files copied to the new filesystem have the hard links preserved or separate copies are created for the linked files. XCU ERN 53 pwd -P and the $PWD variable Reject The standard is clear. This appears to point to bugs in many implementations. XCU ERN 54 mailx Accept as marked below Note well, that this overrides ERN 20. Change resolution to #20 as follows If the current message has not been written (for example, by the print command) since mailx started or since any other message was the current message, behave as if the print command was entered. Otherwise, if there is an undeleted message after the current message, make it the current message and behave as if the print command was entered. Otherwise, an informational message to the effect that there are no further messages in the mailbox shall be written, followed by the mailx prompt. Should the current message location be the result of an immediately preceeding "hold", "mbox", "preserve", or "touch" command, next will act as if the current message has already been written. (i.e. just add "mbox" and "touch" to the list of commands at the bottom). Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. XBD ERN 53 is the first itenm The next call is April 21 2005 irc://irc.freestandards.org/austin