Minutes of the 17th September 2009 Teleconference Austin-465 Page 1 of 1 Submitted by Andrew Josey, The Open Group. September 18 , 2009 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Nick Stoughton, USENIX, ISO/IEC OR Ulrich Drepper, Red Hat Nick reported that the ISO/IEC edition of the standard has now been published. We discussed mail sequence 12733 where Geoff has proposed some dispositions for interpretations. We proceeded to update Mantis bugs 50,52,63 and 66 to add interpretations status. # 50 , the standard is ambiguous # 52 , the standard has a defect # 63 , the standard is ambiguous # 66 , the standard has a defect We then proceeded to review some of the new bugs # 139 PATH needs same // treatment as CDPATH Accept http://austingroupbugs.net/view.php?id=139 It was agreed that this should have an interpretation raised for the defect case. Interpretation response: The standard states the requirements for PATH and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor." Rationale: This is for consistency with the previous change to CDPATH made in interpretation 1003.1-2001 #199 https://www.opengroup.org/austin/interps/uploads/40/15188/AI-199.txt [^] Notes to the Editor (not part of this interpretation): Make the change suggested by the submitter # 141 O_NONBLOCK Accept as marked http://austingroupbugs.net/view.php?id=141 Interpretation required: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor Rationale: None. Notes to the Editor (not part of this interpretation): Make the change At page 807 line 26910 (fcntl F_SETFL), add a sentence: If fildes does not support non-blocking operations, it is unspecified whether the O_NONBLOCK flag will be ignored. At line 45239 (open O_NONBLOCK), change: Otherwise, the behavior of O_NONBLOCK is unspecified. to: Otherwise, the O_NONBLOCK flag shall not cause an error, but it is unspecified whether the file status flags will include the O_NONBLOCK flag. # 142 alphasort prototype Reject http://austingroupbugs.net/view.php?id=142 The alphasort function must be made typesafe, so we do not intend to change this. # 143 readlinkat return value Accept http://austingroupbugs.net/view.php?id=143 It was agreed an interpretation is required Interpretation response: The standard states the requirements for readlinkat() and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: None. Notes to the Editor (not part of this interpretation): Make changes as suggested by the submitter # 145 Download Closed http://austingroupbugs.net/view.php?id=145 This is not a bug in the standard. The matter has been passed to those responsible for the web site who have responded. Next Steps ---------- The next call will be on Sep 24 at 16:00 UK time/08:00 Pacific to carry on with the defect reports http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freestandards.org #austin ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic