Minutes of the 2nd March 2023 Teleconference Austin-1295 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 4th March 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR (partial) Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR (partial) Don Cragun, IEEE PASC OR Apologies Eric Ackermann, HPI, University of Potsdam Tom Thompson, IEEE * General news The IEEE Mandatory Editorial Coordination comments have been received and we are still working through them. This is liable to take a couple of weeks. We will forward some proposed changes to the core team for discussion at the next meeting. * Carried Forward This section trimmed -- see Austin/1264 Bug 1406: clarification of SEEK_END when current pointer doesn't match buffer size OPEN https://austingroupbugs.net/view.php?id=1406 Actions carried forward: ACTION: Andrew to contact Rich Felker (dalias) and Alan Coopersmith (Solaris) for feedback. Completed ACTION: Eric B to contact glibc folks. Bug 1616: Standardize mktemp utility OPEN https://austingroupbugs.net/view.php?id=1616 We will need a sponsor; it is not suitable for inclusion in Issue 8. ACTION: Eric to ask The Open Group to sponsor adding the mktemp utility (for Issue 9). Bug 1291: Add method to obtain pthread attributes OPEN https://austingroupbugs.net/view.php?id=1291 Needs additional details and sponsor for Issue 9 Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 (brought forward) Don has an action to produce a proposal. Bug 1622: Standardize getpeereid function OPEN https://austingroupbugs.net/view.php?id=1622 Action: Eric B to ask The Open Group if they are willing to sponsor this function for Issue 9. * Current Business Bug 1629: Shell vs. read(2) errors on the script OPEN https://austingroupbugs.net/view.php?id=1629 A reminder that this item it is being left open for feedback until 2023-03-09. Bug 1630: Alias names https://austingroupbugs.net/view.php?id=1630 OPEN We discussed this at length and a proposal has been entered into the etherpad for feedback. See https://posix.rhansen.org/p/2023-02-27 Bug 1632: Tilde expansions with HOME="" or HOME value ending in / Accepted as Marked https://austingroupbugs.net/view.php?id=1632 This item is tagged for TC3-2008 On page 2320 line 74793 section 2.6.1, change: The pathname resulting from tilde expansion shall be treated as if quoted to prevent it being altered by field splitting and pathname expansion. to: The pathname that replaces the tilde-prefix shall be treated as if quoted to prevent it being altered by field splitting and pathname expansion; if a follows the tilde-prefix and the pathname ends with a , the trailing from the pathname should be omitted from the replacement. If the word being expanded consists of only the character and HOME is set to the null string, this produces an empty field (as opposed to zero fields) as the expanded word. Note: A future version of this standard may require that if a follows the tilde-prefix and the pathname ends with a , the trailing from the pathname is omitted from the replacement. Bug 1633: Add memrchr OPEN https://austingroupbugs.net/view.php?id=1633 Action: Eric B to ask The Open Group Base Working Group if they will sponsor for Issue 9. In addition to memchr(), the standard also includes wmemchr(). Does this request also intend to add wmemrchr()? Bug 1634: mailx: more clarification on system mailbox OPEN https://austingroupbugs.net/view.php?id=1634 We started on this item and will continue next time. Next Steps ---------- The next calls are on: Mon 2023-03-06 (general bugs) Thu 2023-03-09 (general bugs) The calls are for 90 minutes Apologies in advance: Geoff Clare, 2023-03-06 Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup)