Minutes of the 14 November 2013 Teleconference Austin-634 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 15th November 2013 Attendees Richard Hansen, BBN Mark Brown Mark Ziegast Joerg Schilling, Fraunhofer Society Geoff Clare, The Open Group Don Cragun, PASC OR David Clissold, IBM Martin Rehak, Oracle Eric Blake, Red Hat Nick Stoughton, USENIX, ISO/IEC OR Apologies Andrew Josey, The Open Group * General news Andrew still needs to chase up the status of the replacement OR for The Open Group (he has sent a mail to the Base WG calling for the replacment). * Outstanding actions +Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don has an action to produce a proposal. +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Eric has an action to update the proposal. +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000592: consistent use of struct timespec OPEN http://austingroupbugs.net/view.php?id=592 Jim had provided additional information in bugnote 1627. This was discussed and Jim took an action to provide further information. +Bug 0000598: OH shading and new interfaces OPEN http://austingroupbugs.net/view.php?id=598 Eric has an action to propose a new solution with self-contained headers. +Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 Action on Joerg to look at this. +Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe OPEN http://austingroupbugs.net/view.php?id=633 We noted that feedback has settled down on the mailing list, and will discuss next session. +Bug 0000657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN http://austingroupbugs.net/view.php?id=657 Eric has an action to propose wording to clarify the behavior for fmemopen(), and also to contact the glibc developers to get their feedback. +Bug 0000658: Undefined/unspecified behavior clauses in description of open have race conditions OPEN http://austingroupbugs.net/view.php?id=658 It was noted that there is some overlap with changes in TC1. Eric took an action to update the proposal to resolve the overlaps appropriately. +Bug 0000615: pthread_setcancelstate should be async-signal-safe OPEN http://austingroupbugs.net/view.php?id=615 We now have reports on AIX and Apple. Jim to report back on whether pthread_cancelstate() is async-signal-safe on Solaris. Andrew to ask HP whether pthread_cancelstate() is async-signal-safe on HP-UX. +Bug 622 left open pending resolution of 615. http://austingroupbugs.net/view.php?id=622 +Bug 0000672: Necessary step(s) to synchronize filename operations on disk OPEN http://austingroupbugs.net/view.php?id=672 Geoff has a new proposed resolution in note 1618. Decided to solicit input from FS developers. Eric to go to Linux, David to AIX and Jim to Solaris. Jim has completed his action (see bugnote 1691). Andrew should chase HP and Apple for input. +Bug 0000663: Specification of str[n]casecmp is ambiguous reopened http://austingroupbugs.net/view.php?id=663 Action on David to follow up with the IBM developers about the EBCDIC collation sequence. Bug 696 either NAME_MAX shouldn't be optional, or readdir_r() needs clarification http://www.austingroupbugs.net/view.php?id=696 Don has an action to propose a resolution. Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 This item is still open. * Current Business * related to Bug 765 (from last week) Action on Eric to file a new Issue 8 bug to implement the pthread_kill() FUTURE DIRECTIONS from bug 765, to include a definition of "Thread Lifetime" and possibly one for "Zombie Thread" if he can find a place to use it in normative text. Eric reported he has not had time to complete this yet. Bug 000768: add "fd-private" POSIX locks to spec OPEN http://austingroupbugs.net/view.php?id=768 This was discussed during the November 14, 2013 conference call. Although we agree that a new lock type might be a good idea, before we could consider anything, we would need actual changes to be added to the text to define the behavior of this feature. Furthermore, there would have to be an existing implementation that is shipping as part of a product. This bug will be kept open for a while as a placeholder for such a specification. Bug 0000769: Add support for SHELL in make Accepted as Marked http://austingroupbugs.net/view.php?id=769 This item is tagged for TC2-2008. After page 2950 line 97668, insert a new bullet: * Specifying an alternate shell to use to process commands. On page 2952 lines 97755-97758, change: The historical MAKESHELL feature was omitted. In some implementations it is used to let a user override the shell to be used to run make commands. This was confusing; for a portable make, the shell should be chosen by the makefile writer or specified on the make command line and not by a user running make. to: The historical MAKESHELL feature, and related features provided by other make implementations, were omitted. In some implementations it is used to let a user override the shell to be used to run make commands. This was confusing; for a portable make, the shell should be chosen by the makefile writer. Further, a makefile writer cannot require an alternate shell to be used and still consider the makefile portable. While it would be possible to standardize a mechanism for specifying an alternate shell, existing implementations do not agree on such a mechanism, and makefile writers can already invoke an alternate shell by specifying the shell name in the rule for a target (e.g., python -c "foo"). Bug 0000770: Add support for .ONESHELL in make OPEN http://austingroupbugs.net/view.php?id=770 We discussed 770 and Eric took an action to contact the GNU make maintainers to ask if they would be willing to extend .ONESHELL to make it more flexible. For example, make it take a target list like .IGNORE, or have a way to turn it on and off (push/pop). We are concerned in particular with how it affects include files, which might be written by different authors. Likewise for multiple files specified with -f. Next Steps ---------- The next call is on November 21, 2013 (a Thursday) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#