Minutes of the 18th July 2024 Teleconference
All, Enclosed are the minutes from this weeks meeting, regards Andrew -- Minutes of the 18th July 2024 TeleconferenceAustin-1418 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th July 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, CISPA Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies Tom Thompson, IEEE * General news A reminder that we have agreed there will be no Monday meetings for a while. Andrew is out on vacation on 1st August so will setup a different webex bridge for that meeting and check Geoff can login ok as the host. The html version of the standard is considered development complete and will be released by the end of the week (completed after the meeting). As noted previously, the ISO/IEC ballot closed on June 28 and passed with 100% approval. We discussed the set of comments received back from the ISO editors. Application of them would be at odds with the project goals which are one identical standard adopted by the three standards bodies. Andrew will prepare a written response to each of the comments indicating why in nearly all cases we would not want to apply to the dociument. It was noted that the first comment says it is mandatory to apply, and if we fail to do so the project will fail at the next stage. We discussed the option if it fails, that is to fallback to the IEEE/ISO PSDO process. Andrew took an option to discuss with Tom prior to submitting the formal response back to ISO. * Current Business Bug 1840: Footnote incorrectly says the time utility is in the UP option Accepted https://www.austingroupbugs.net/view.php?id=184 This item is tagged for TC1-2024. Bug 1628: Add -o (reopen stdin) option to xargs(1) OPEN https://austingroupbugs.net/view.php?id=1628 We discussed this at length. See the etherpad for notes. Next Steps -- The next calls are on Thu 2024-07-25 (WEBEX meeting - general bugs) Thu 2024-08-01 (WEBEX meeting - general bugs) **Different Bridge** The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Austin Group Status/1003.1 Status Report July 2024
Dear all Enclosed the latest summary status report regards Andrew --- Austin Group Status/1003.1 Status ReportAustin-1417 Page 1 of 1 Submitted by Andrew Josey, The Open Group July 20, 2024 The Austin Common Standards Revision Group (CSRG) is a joint technical working group established to develop and maintain the core open systems interfaces that are the POSIX® 1003.1 (and former 1003.2) standards, ISO/IEC 9945, and the core of the Single UNIX Specification. The working group brings together the technical experts from ISO JTC1, IEEE and The Open Group. The previous revision to the 1003.1 standard was published in January 2018. The 2024 revision was approved by The Open Group on March 21 2024, and by the IEEE on May 21 2024. The pdf editions were published on June 14 2024. The online html edition published on July 19 2024. The document has completed balloting at ISO/IEC and passed. It is being prepared for publication. The group meets regularly via teleconference to discuss defect reports and enhancement requests on the standard. Minutes are recorded in the Document register at https://www.opengroup.org/austin/docreg.html. The group uses an online system for reporting defects and enhancement requests for the standard at https://austingroupbugs.net . The next working group meeting is listed at https://www.opengroup.org/austin/ in the events diary. Further information on the Austin Group can be obtained at https://www.opengroup.org/austin/faq.html Respectfully submitted, Andrew Josey, The Open Group, 1003.1 Chair Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Availability of online html version
Dear all I am pleased to announce that the html version of the 2024 edition is now available to read online, more information and registration at http://publications.opengroup.org/c243 Registration helps us to track interest, once registered you can bookmark the direct page within pubs.opengroup.org. Please use the Online Pubs project for reporting any issues using Mantis. We’ll give it a few weeks for any feedback before we put up the download bundles. regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
9945 Project Editor Status Report July 2024
All Enclosed is the 9945 Project Editor Status Report submitted this week to ISO/IEC JTC 1 SC22 for their September plenary meeting regards Andrew --- 9945 Project Editor Status Report Austin-1416 Page 1 of 1 Submitted by Andrew Josey, The Open Group July 15, 2024 The Austin Common Standards Revision Group (CSRG) is a joint technical working group established to develop and maintain the core open systems interfaces that are the POSIX™ 1003.1 (and former 1003.2) standards, ISO/IEC 9945, and the core of the Single UNIX® Specification. The working group brings together the technical experts from ISO JTC 1, IEEE and The Open Group. The approach to specification development is "write once, adopt everywhere", with the deliverables being a set of specifications that carry the IEEE POSIX designation, The Open Group Standard designation, and the ISO/IEC POSIX designation. The current set of specifications is simultaneously ISO/IEC 9945, IEEE Std 1003.1 and forms the core of the Single UNIX Specification. Recent activities have been focused on the development of a major revision, as well as handling defect reports. The DIS ballot for the revision ended at the end of June 2024 and passed. The document is now being prepared for publication. At the same time the document has also been approved and published by The Open Group and the IEEE, as The Open Group Base Specifications, Issue 8, and IEEE Standard 1003.1-2024 respectively. Experts from National Bodies wishing to be involved in the maintenance of the standard are welcome, and should contact the chair of the WG (Andrew Josey). The group meets regularly via teleconference to discuss defect reports and enhancement requests on the standard. Minutes are recorded in the Document register at https://www.opengroup.org/austin/docreg.html. The group uses an online system for reporting defects and enhancement requests for the standard at https://austingroupbugs.net . The next working group meeting is listed at https://www.opengroup.org/austin/ in the events diary. Further information on the Austin Group can be obtained at https://www.opengroup.org/austin/faq.html Respectfully submitted, Andrew Josey 9945 Project Editor. ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 11th July 2024 Teleconference
All Enclosed are the minutes from yesterday’s meeting regards Andrew --- Minutes of the 11th July 2024 TeleconferenceAustin-1415 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 12th July 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Ahmet Acar Apologies Tom Thompson, IEEE Eric Ackermann, CISPA * General news A reminder that we have agreed there will be no Monday meetings for a while. The IEEE and The Open Group pdf edition was published on Friday June 14th. The html version is in progress and a preview will be made available to the Core team to send feedback on. At the moment the known outstanding issues are some table layouts and the search functions not enabled. The ISO/IEC ballot closed on June 28 and passed with 100% approval. A set of comments were received from the ISO editors. Andrew has sent an informal response back to Bill Ash. Andrew will take an action to send a formal response back with the general direction that we do not want to apply the changes as the style is as previously agreed over the years. Andrew noted that the SC22 plenary will be held in London in September and he plans to attend at least one day. He will draft a 9945 project editor status report to submit. * Current Business Bug 1835: Malformatted ls STDOUT description for -i Accepted https://austingroupbugs.net/view.php?id=1835 This item is tagged for TC1-2024. Bug 1836: Missing statements about reading from standard input Accepted https://austingroupbugs.net/view.php?id=1836 This item is tagged for TC1-2024. Bug 1837: Editorial mistakes in function names Accepted https://austingroupbugs.net/view.php?id=1837 This item is tagged for TC1-2024. Bug 1838: Table row formatted like a header Accepted https://austingroupbugs.net/view.php?id=1838 This item is tagged for TC1-2024. Bug 1839: Incorrect use of "sup" in FLT_MIN eqn formula Accepted https://austingroupbugs.net/view.php?id=1839 This item is tagged for TC1-2024. Other business We discussed Bug 1628 and will continue on it next time. Bug 1628: Add -o (reopen stdin) option to xargs(1) https://austingroupbugs.net/view.php?id=1628 Next Steps -- The next calls are on Thu 2024-07-18 (WEBEX meeting - general bugs) Thu 2024-07-25 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 20th June 2024 Teleconference
All Enclosed are the minutes of yesterdays’ call. The next meeting is July 11th regards Andrew --- Minutes of the 20th June 2024 TeleconferenceAustin-1414 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 21st June 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev * General news A reminder that we have agreed there will be no Monday meetings for a while. The IEEE and The Open Group pdf edition was published on Friday June 14th. The html version is in progress and will take a few more weeks to complete. The ISO/IEC ballot closes on June 28. Andrew has setup the Issue 8 project in Mantis. We agreed to cancel the meeting on June 27th. With the July 4th holiday, this means the next meeting is July 11th. * Current Business We reviewed the following 5 bugs to confirm the interpretation text was correct. Andrew took an action to start the interpretation timer on these (complted after the meeting). Bug 1798: Must posix_getdents remember file offsets across exec? https://austingroupbugs.net/view.php?id=1798 Bug 1799: endian.h unconditionally requires 64-bit integers https://austingroupbugs.net/view.php?id=1799 Bug 1806: ambiguous description of which attributes `unset` unsets in case of readonly attribute being set https://austingroupbugs.net/view.php?id=1806 Bug 1813: generic xargs description cleanups https://austingroupbugs.net/view.php?id=1813 Bug 1821: Define the values of $0, $1, etc. in the END section https://austingroupbugs.net/view.php?id=1821 Other business We discussed bug 1834: Bug 1834: strnlen() & wcsnlen() descriptions use of "terminating" NUL character https://www.austingroupbugs.net/view.php?id=1834 Leave open until these functions have been adopted or rejected for inclusion in C2Y. We believe that the wording in the Desired Action is better than the current wording in the standard. Nick took an action to e-mail Chris Bazely with this as the direction to which POSIX is leaning. (completed during the meeting) Bug 1635: iconv: please be more explicit in input-not-convertible case https://austingroupbugs.net/view.php?id=1635 We will continue on this item next time, see the etherpad for details. Next Steps -- The next call is on: Thu 2024-07-11 (WEBEX meeting - general bugs) No meetings on Thu 2024-06-27, Thu 2024-07-04 The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Re: Procedural questions with regard to publication of Issue 8.
hi all We would indeed prefer issues against the latest release but as it will take up to a month for that to be published in html do not have a problem accepting bug reports on other releases. In general we can cope with whatever version is picked although all future changes will be to Issue 8 We will see if we have options to change the Mantis setup to prevent old releases being selected regards Andrew > On 21 Jun 2024, at 05:49, Niu Danny via austin-group-l at The Open Group > wrote: > > Hi all. > > Since Issue 8 is published, we no longer submit issues to the previous > projects (i.e. Issue7+TC*, drafts) right? Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Interpretations starting a final 30 day review
Dear all The following bugs have interpretations proposed and are starting a 30 day final review. Bug 1798: Must posix_getdents remember file offsets across exec? https://austingroupbugs.net/view.php?id=1798 Bug 1799: endian.h unconditionally requires 64-bit integers https://austingroupbugs.net/view.php?id=1799 Bug 1806: ambiguous description of which attributes `unset` unsets in case of readonly attribute being set https://austingroupbugs.net/view.php?id=1806 Bug 1813: generic xargs description cleanups https://austingroupbugs.net/view.php?id=1813 Bug 1821: Define the values of $0, $1, etc. in the END section https://austingroupbugs.net/view.php?id=1821 Comments are due back, if any, before July 22 2024 best regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 13th June 2024 Teleconference
All Enclosed are the minutes of this weeks meeting regards Andrew Minutes of the 13th June 2024 TeleconferenceAustin-1413 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 14th June 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Ahmet Acar Tom Thompson, IEEE Apologies Mark Ziegast, SHware Systems Dev * General news A reminder that we have agreed there will be no Monday meetings for a while. Andrew reminded everyone that the pdf version of the standard will be published by IEEE and The Open Group this friday June 14. The html version is still to be progressed. The ISO/IEC ballot closes on June 28. Andrew took an action to setup the Issue 8 project for bug reporting in Mantis. Strnlen() in C We discussed the C committee's wording for strnlen() and wcsnlen() in C2y. That proposal uses string where we are careful to avoid that (since, by definition a string must be terminated by a null byte). AI: Nick to point out the ambiguity to the C committee. * Current Business Bug 1833: Ambiguity about empty string used as option-argument Accepted as Marked https://www.austingroupbugs.net/view.php?id=1833 This item is tagged for TC1-2024 Change: However, a conforming implementation shall also permit applications to specify the option and option-argument in the same argument string without intervening characters. to: However, a conforming implementation shall also permit applications to specify the option and a non-empty option-argument in the same argument string without intervening characters. Bug 1635: iconv: please be more explicit in input-not-convertible case OPEN https://austingroupbugs.net/view.php?id=1635 We discussed this item since Bruno added some notes to the bug on June 11th and 12th. Based on the discussions of the 2024-06-13 call, the Austin Group understands the desire to have a means for an iconv() implementation that stops early when a transliteration is not possible, despite recognizing valid characters in the input. Would it work to utilize a different errno in this sequence, perhaps ENOTSUP or EPROTO, to make it easier for applications to distinguish between a stop because of unrecognized input (EILSEQ) vs unrepresentable output (the new errno)? [bugnote:6812 mentioned ICONV_SET_* flags on MacOS; that appears to be used with a non-standard interface iconvctl(), and while it may be possible to standardize that interface and a new ICONV_SET_* flag as a means for for opting into the new errno value behavior, it seems like a much bigger request at this time] Regarding the different defaults, we could add //NOTRANSLIT and make it unspecified whether //TRANSLIT or //NOTRANSLIT is the default. We will continue on this item next time. Items carried forward: Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1824: cp: directories and symlinks OPEN https://austingroupbugs.net/view.php?id=1824 Action: Eric B to contact the GNU coreutils maintainers to ask for their input, particularly on the behavior noted in bugnote 6788. Bug 1831: how do you get the timestamp resolution of a symlink? OPEN https://austingroupbugs.net/view.php?id=1831 Action: EricB to ask The Open Group to sponsor this change. Next Steps -- The next call is on: Thu 2024-06-20 (WEBEX meeting - general bugs) Thu 2024-06-27 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 6th June 2024 Teleconference
All Enclosed are the minutes from yesterdays call. Please note the next meeting is Thursday June 13. regards Andrew --- Minutes of the 6th June 2024 TeleconferenceAustin-1411 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 7th June 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Ahmet Acar Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev * General news We agreed there will be no Monday meetings for a while. Andrew reported that the pdf document was ready for publication by IEEE and The Open Group and is due for publication on June 14. The html version is still to be progressed. The ISO/IEC ballot closes on June 28. * Current Business Bug 1832: Add preadv() and pwritev() https://austingroupbugs.net/view.php?id=1832 OPEN Based on feedback from Philip Guenther in email sequence #37374, we changed our comment on this proposal during the 2024-06-06 meeting to: Given that all versions of read and write operations in the standard have been cancellation points for as long as threads were present, saying that pread() and pwrite() are no longer required to be cancellation points would mean applications that are depending on them to act on a pending cancellation would have to be changed to perform their own cancellation point processing (calling pthread_testcancel()) when performing these operations. Furthermore, all known implementations of these functions have made them cancellation points. Given that preadv() and pwritev() are logically equivalent to pread() and pwrite(), we believe that they should also be cancellation points. Action: EricB to ask The Open Group to sponsor this change for issue 9. 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 Nick has completed his action here. We reviewed the draft at the meeting, see Austin/1412. Items carried forward: Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1824: cp: directories and symlinks OPEN https://austingroupbugs.net/view.php?id=1824 Action: Eric B to contact the GNU coreutils maintainers to ask for their input, particularly on the behavior noted in bugnote 6788. Bug 1831: how do you get the timestamp resolution of a symlink? OPEN https://austingroupbugs.net/view.php?id=1831 Action: EricB to ask The Open Group to sponsor this change. Next Steps -- Reminder: Mon 2024-06-10 No meeting The next call is on: Thu 2024-06-13 (WEBEX meeting - general bugs) Thu 2024-06-20 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 30th May 2024 Teleconference
All Enclosed are the minutes from the Thursday meeting this week. Please note that there is NO meeting on Monday June 3rd. regards Andrew -- Minutes of the 30th May 2024 TeleconferenceAustin-1410 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 1st June 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Apologies Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev * General news There will be no meeting on Monday June 3rd We discussed the front matter of the document which is being prepared for publication. Andrew took an action to send the latest draft to the Austin Core team for a quick review. We are still aiming to publish on June 14. The ISO/IEC ballot closes on June 28. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 Nick has the action here, and has completed an initial draft which we will review at the next meeting. Items carried forward: Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1824: cp: directories and symlinks OPEN https://austingroupbugs.net/view.php?id=1824 Action: Eric B to contact the GNU coreutils maintainers to ask for their input, particularly on the behavior noted in bugnote 6788. Bug 1831: how do you get the timestamp resolution of a symlink? OPEN https://austingroupbugs.net/view.php?id=1831 Action: EricB to ask The Open Group to sponsor this change. New business: Bug 1832: Add preadv() and pwritev() https://austingroupbugs.net/view.php?id=1832 OPEN We believe that preadv() and pwritev() should be cancellation points. Reading/writing to a file system across a network can certainly have unbounded delays. Action: EricB to ask The Open Group to sponsor this change for issue 9. We ended the meeting after 20 minutes. Next Steps -- Reminder: Mon 2024-06-03 No meeting The next call is on: Mon 2024-06-03 No Meeting Thu 2024-06-06 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Austin Group Status/1003.1 Status Report
All Attached is a brief status report regards Andrew -- Austin Group Status/1003.1 Status ReportAustin-1409 Page 1 of 1 Submitted by Andrew Josey, The Open Group May 24, 2024 The Austin Common Standards Revision Group (CSRG) is a joint technical working group established to develop and maintain the core open systems interfaces that are the POSIX® 1003.1 (and former 1003.2) standards, ISO/IEC 9945, and the core of the Single UNIX Specification. The working group brings together the technical experts from ISO JTC1, IEEE and The Open Group. The last revision to the 1003.1 standard was published in January 2018. A new revision has now been approved by The Open Group on March 21 2024, and by the IEEE on May 21 2024. We expect this new revision to be published in mid June 2024. The draft is also undergoing ballot at ISO/IEC and that is expected to complete at the end of June 2024. The group meets regularly by teleconference to consider defect reports and issues on the standard. Minutes are kept in the Document register at http://www.opengroup.org/austin/docreg.html . The group uses an online defect reporting system for maintenance of the standard, see http://austingroupbugs.net The next working group meeting is listed at http://www.opengroup.org/austin/ in the events diary. Further information on the Austin Group can be obtained at http://www.opengroup.org/austin/faq.html Respectfully submitted, Andrew Josey, The Open Group, 1003.1 Chair Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 23rd May 2024 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew --- Minutes of the 23rd May 2024 TeleconferenceAustin-1408 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 24th May 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Ackermann, CISPA Paul Eggert Ahmet Acar (joined late) Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev Eric Blake, Red Hat, The Open Group OR * General news There will be no meeting on Monday May 27. IEEE approval was achieved on May 21 as IEEE Standard 1003.1-2024. Andrew noted we are preparing the document, which is due for publication on June 14. We are working on the frontmatter and participants lists have been posted for final feedback by close of business Monday May 27. The ISO/IEC ballot closes on June 28. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We spent the meeting discussing this item. The meeting concluded the following: >> For %z and %Z, requiring applications to set tm_zone and tm_gmtoff >>would create a conflict with the C standard. C17 says that the only >>member used by %z and %Z is tm_isdst. >There’s no conflict here. C17 does not specify the method used to >deduce the time zone used for %z and %Z. An implementation is free >to use whatever screwy method it likes. Only the C committee can give a definitive answer on what C17 requires here. We cannot finalise new wording for %z and %Z until we liaise with them. Therefore our next step on this bug should be to prepare a paper for Nick to submit for consideration by the C committee. Items carried forward: Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1824: cp: directories and symlinks OPEN https://austingroupbugs.net/view.php?id=1824 Action: Eric B to contact the GNU coreutils maintainers to ask for their input, particularly on the behavior noted in bugnote 6788. Bug 1831: how do you get the timestamp resolution of a symlink? OPEN https://austingroupbugs.net/view.php?id=1831 Action: EricB to ask The Open Group to sponsor this change. Next Steps -- Reminder: Mon 2024-05-27 No meeting The next call is on: Thu 2024-05-30 (WEBEX meeting - general bugs) Mon 2024-06-03 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Approvals and participants listings in the front matter
Dear all We are pleased to announce that IEEE has approved the draft as the 2024 edition of the 1003.1 standard. The document has also been approved at The Open Group. We are now completing the document for publication. In the document front matter we list the participants. We have two lists of participants from the Austin Group: Austin Group participants: (people who sent an email to austin-group-l since mid 2016 - i.e. after TC2) Austin Group reviewers: (people who submitted Mantis bugs that were applied in Issue 8) These lists are available to review at https://www.opengroup.org/austin/restricted/participants/ (login required) Please review (check spelling, accents etc.) and feed comments back asap and no later than Monday May 27. If you feel you are missing please contact me directly regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 20th May 2024 Teleconference
All
Enclosed are the minutes of the Monday call this week.
Note that since the call we received formal news of the approval
of the document by IEEE:
"I am pleased to inform you that P1003.1 was approved as a revised standard by
the IEEE SA Standards Board on 20 May 2024."
regards
Andrew
Minutes of the 20th May 2024 TeleconferenceAustin-1406 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 22nd May 2024
Attendees:
Don Cragun, IEEE SA OR
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Apologies
Tom Thompson, IEEE
Mark Ziegast, SHware Systems Dev
Eric Ackermann, CISPA
Eric Blake, Red Hat, The Open Group OR (joining late)
* General news
There will be no meeting on Monday May 27.
The approval vote on 1003.1 closes today (after the meeting
we received notice of approval as IEEE Standard 1003.1-2024)
The ISO/IEC ballot closes on June 28.
* Current Business
1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797
We expect to continue this item this coming Thursday
(Paul has confirmed availability).
Bug 1818: Add strcasestr() & strcasestr_l() OPEN
https://austingroupbugs.net/view.php?id=1818
Action: Eric B to ask The Open Group if they are willing to sponsor
these functions for Issue 9.
Bug 1822: Define splitting using a null field separator Accepted as Marked
https://austingroupbugs.net/view.php?id=1822
This item is tagged for Issue 9.
Page and line numbers are for issue 8 draft 4.1.
On P2617, L85671 section awk (EXTENDED DESCRIPTION) change:
If FS is a null string, the behavior is unspecified.
to:
If FS is a null string, each character shall become a separate field.
We started on this item. Notes are in the etherpad. We will continue
on this item next time.
Bug 1824: cp: directories and symlinks OPEN
https://austingroupbugs.net/view.php?id=1824
Action: Eric B to contact the GNU coreutils maintainers to ask for
their input, particularly on the behavior noted in bugnote 6788.
Bug 1825: Does releasing a reader lock carries a "release" memory order
semantic? Withdrawn
https://austingroupbugs.net/view.php?id=1825
Withdrawn by the submitter.
Bug 1826: du: space used between and , while common
implementations use tab Rejected
https://austingroupbugs.net/view.php?id=1826
Bug 1827: Standardize gzip(1) cli interface instead of adding it to compress(1)
Rejected
https://austingroupbugs.net/view.php?id=1827
Bug 1041 was resolved more than 7 years ago and had been included
in draft versions of the standard for more than 4 years before bug
1827 was submitted. Filing a bug to reverse this after the IEEE
and The Open Group ballots have been completed and while the ISO
ballot on the current version of the standard is in its final stage
is way too late to make the requested changes. Furthermore, these
issues were discussed before the changes were approved seven years
ago and the standard developers believed then and still believe
that including the changes to compress was better than adding several
other sets of compression utilities. Therefore, this bug is rejected.
Bug 1828: Rationale is out of date Accepted
https://austingroupbugs.net/view.php?id=1828
This item is tagged for TC1-2024
Bug 1829: symlink() and terminating null bytes Accepted as Marked
https://austingroupbugs.net/view.php?id=1829
This item is tagged for TC1-2024
Make the changes suggested in the Desired Action and in Note: 0006776.
Bug 1830: off-by-one error regarding offset maximum Accepted as Marked
https://austingroupbugs.net/view.php?id=1830
This item is tagged for TC1-2024
Change:
For regular files, no data transfer shall occur past the offset
maximum established in the open file description associated
with fildes.
to:
For regular files, no data shall be written at positions greater
than or equal to the offset maximum established in the open
file description associated with fildes. If the starting position
is greater than or equal to the offset maximum (and nbyte is
greater than 0), the request shall fail; otherwise, only as
many bytes as there is room for shall be written.
Bug 1831: how do you get the timestamp resolution of a symlink? OPEN
https://austingroupbugs.net/view.php?id=1831
Action: EricB to ask The Open Group to sponsor this change.
Closing 786 as a duplicate of this, since this is more up to date
and refers to an implementation that is expected to exist by the
time this is standardized.
Bug 786: pathconfat() is missing Dup of 1831
https://austingroupbugs.net/view.php?id=786
Closed, duplicate of 1831.
Next Steps
--
The next call is on:
Thu 2024-05-23 (WEBEX meeting - general bugs)
Mon 2024-05-27 No meeting
Thu 2024-05-30 (WEBEX meeting - general bugs)
Apologies in Advance:
Eric Blake 2024-05-20, 2024-05-
Minutes of the 16th May 2024 Teleconference
All Enclosed are the minutes of the thursday meeting this week regards Andrew - Minutes of the 16th May 2024 TeleconferenceAustin-1406 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 18th May 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Ackermann, CISPA Eric Blake, Red Hat, The Open Group OR (joining late) Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev * General news There will be no meeting on Monday May 27. P1003.1 was recommended for approval at the May 6th RevCom meeting. The Standards Association Standards Board (SASB) electronic ballot (e-ballot) vote should close early to mid-week next week. Once closed the RevCom Administrator will typically send an email informing of the final vote. After approval we can moved forward to complete the frontmatter and proceed to publication, and the html conversion. The ISO/IEC ballot closes on June 28. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1821: Define the values of $0, $1, etc. in the END section Accepted as Marked https://austingroupbugs.net/view.php?id=1821 An interpretation required, This is tagged for TC1-2024. Interpretation response: 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: The standard requires that the value of NF is retained in an END section, but does not state what the values of the fields $1 through $NF are, despite requiring them to exist. Notes to the Editor (not part of this interpretation): Page and line numbers are for Issue 8 draft 4.1. At page 2614 line 85574 (FILENAME), delete: Inside an END action the value shall be the name of the last input file processed. At page 2614 line 85578 (FNR), change: Inside an END action the value shall be the number of the last record processed in the last file processed. to: If an application changes the value of FNR, the results are unspecified. At page 2614 line 85581 (NF), change: The number of fields in the current record. Inside a BEGIN action, the use of NF is undefined unless a getline function without a var argument is executed previously. Inside an END action, NF shall retain the value it had for the last record read, unless a subsequent, redirected, getline function without a var argument is performed prior to entering the END action. to: The number of fields in the current record. Inside the first BEGIN action, the value shall initially be zero, except that if the -v option was used to assign a value to NF it is unspecified whether that value is retained or the value is reset to zero. At page 2614 line 85587 (NR), change: Inside an END action the value shall be the number of the last record processed. to: If an application changes the value of NR, the results are unspecified. At page 2618 after line 85708 (Special Patterns), add: Entering an END action shall not alter the value of any fields or variables that had previously been set. Bug 1822: Define splitting using a null field separator OPEN https://austingroupbugs.net/view.php?id=1822 We started on this item. Notes are in the etherpad. We will continue on this item next time. Next Steps -- The next call is on: Mon 2024-05-20 (WEBEX meeting - general bugs) Mon 2024-05-27 No meeting Thu 2024-05-23 (WEBEX meeting - general bugs) Apologies in Advance: Eric Blake 2024-05-20, 2024-05-23 The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 13th May 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew - Minutes of the 13th May 2024 TeleconferenceAustin-1405 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 15th May 2024 Attendees: Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE SA OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Brooks Harris Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev * General news There will be no meeting on Monday May 27. The general news is unchanged. The IEEE Revcom committee met on May 6 to consider approval of draft 4.1. We have yet to hear the result. After approval we can moved forward to complete the frontmatter and proceed to publication, and the html conversion. The ISO/IEC ballot closes on June 28. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1820: The impact of changing NF should be stated Accepted as Marked https://austingroupbugs.net/view.php?id=1820 This item is tagged for Issue 9. On Issue 8 draft 4.1 page 2613 line 85507, change: Field variables shall be designated by a '$' followed by a number or numerical expression. The effect of the field number expression evaluating to anything other than a non-negative integer is unspecified; uninitialized variables or string values need not be converted to numeric values in this context. New field variables can be created by assigning a value to them. References to nonexistent fields (that is, fields after $NF), shall evaluate to the uninitialized value. Such references shall not create new fields. However, assigning to a nonexistent field (for example, $(NF+2)=5) shall increase the value of NF; create any intervening fields with the uninitialized value; and cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Each field variable shall have a string value or an uninitialized value when created. Field variables shall have the uninitialized value when created from $0 using FS and the variable does not contain any characters. If appropriate, the field variable shall be considered a numeric string (see Expressions in awk, on page 2608). to: Field variables shall be designated by a '$' followed by a number or numerical expression. The effect of the field number expression evaluating to anything other than a non-negative integer is unspecified; uninitialized variables or string values need not be converted to numeric values in this context. Each field variable shall have a string value or an uninitialized value when created. Field variables shall have the uninitialized value when created from $0 using FS and the variable does not contain any characters. If appropriate, the field variable shall be considered a numeric string (see Expressions in awk, on page 2608). New field variables can be created by assigning a value to them. References to nonexistent fields (that is, fields after $NF), shall evaluate to the uninitialized value. Such references shall not create new fields. However, assigning to a nonexistent field (for example, $(NF+2)=5) shall increase the value of NF; create any intervening fields with the uninitialized value; and cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Directly increasing the value of NF (for example, NF += 2) shall have the same effect as assigning an empty string to $NF (where NF has its new value). Decreasing the value of NF to a non-negative value shall remove all fields after $NF and cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Assigning to NF without changing its value (for example, NF = NF) shall cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Bug 1821: Define the values of $0, $1, etc. in the END section OPEN https://austingroupbugs.net/view.php?id=1821 We started on this item. Notes are in the etherpad. We will continue on this item next time. Next Steps -- The next call is on: Thu 2024-05-16 (WEBEX meeting - general bugs) Mon 2024-05-20 (WEBEX meeting - general bugs) Note: Mon 2024-05-27 No meeting The calls are for 90 minutes 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
Correction: Minutes of the 9th May 2024 Teleconference
All
The disposition for bug report 1817 was incorrect. Enclosed are that section of
the corrected minutes (the full document is in the document register)
regards
Andrew
__
Minutes of the 9th May 2024 TeleconferenceAustin-1404 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 10th May 2024
{snip}
Bug 1817: lseek(2) - "size of a file" undefined Accepted as Marked
https://austingroupbugs.net/view.php?id=1817
This item is marked for TC1-2024
On page 965 line 32823 section fstatat(), change:
The value of the st_size member shall be set to the length of
the pathname contained in the symbolic link
to:
The value of the st_size member shall be set to the length of
the contents of the symbolic link
On page 1292 line 43059 section lseek(), change:
the file offset shall be set to the size of the file plus offset.
to:
the file offset shall be set to the size of the file (as would
be returned in st_size by the fstat() function) plus offset;
except that for block special files, it is unspecified whether
the offset is relative to the start of the file or to the
corresponding device's capacity in bytes.
On page 1293 line 43104 section lseek(), add fstat() to SEE ALSO.
{snip}
----
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 9th May 2024 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew -- Minutes of the 9th May 2024 TeleconferenceAustin-1404 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 10th May 2024 Attendees: Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE SA OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies Tom Thompson, IEEE Eric Ackermann, CISPA Mark Ziegast, SHware Systems Dev * General news The general news is unchanged. The IEEE Revcom committee met on May 6 to consider approval of draft 4.1. We have yet to hear the result. After approval we can moved forward to complete the frontmatter and proceed to publication, and the html conversion. The ISO/IEC ballot closes on June 28. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1817: lseek(2) - "size of a file" undefined Accepted as Marked https://austingroupbugs.net/view.php?id=1817 Proposed interpretation (review timer to start after approval of issue 8), using draft 4.0 line numbers . Interpretation response: The standard states that the posix_getdents() function starts reading at the current file offset in the open file description associated with fildes, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Elsewhere the standard makes allowances for implementations where directory streams are not implemented using a file descriptor, but this was not extended to the new posix_getdents() function when it was added. Notes to the Editor (not part of this interpretation): After page 920 line 31407 section fdopendir(), add a new paragraph: If the file descriptor specified by fd is associated with an open file description on which posix_getdents() has previously been used, or for which any associated file descriptor is already associated with a directory stream, the behavior is unspecified. After page 1567 line 52616 section posix_getdents(): The behavior is unspecified if lseek() is used to set the file offset to a value other than zero or a value returned by a previous call to lseek() on the same open file description. add these sentences: The behavior is unspecified if calls to posix_getdents() are made on different file descriptors that refer to the same open file description (for example, before and after a file descriptor is inherited across fork() or the exec family of functions, or is duplicated using dup() or fcntl()), unless lseek() is used to set the file offset to zero in between the calls to posix_getdents(). A single exception to this condition is that after a call to fork(), either the parent or child (but not both) can continue processing the directory using posix_getdents(). Likewise, the behavior is unspecified if in between two calls to posix_getdents() on one file descriptor, the file offset is altered by a call made on a different file descriptor that refers to the same open file description. At page 1568 line 52626 section posix_getdents(), change: If a sequence of calls to posix_getdents() is made that reads from offset zero to end-of-file and a file is removed from or added to the directory between the first and last of those calls, whether the sequence of calls returns an entry for that file is unspecified. to: If a sequence of calls to posix_getdents() is made that reads from offset zero to end-of-file and a directory entry is removed from or added to the directory between the first and last of those calls, whether the sequence of calls returns that directory entry is unspecified. After page 1571 line 52771 section posix_getdents(), add a new paragraph to RATIONALE: The restrictions on the use of different file descriptors that refer to the same open file description are needed in order to enable implementations where directory streams are not implemented using a file descriptor to maintain some internal state related to a particular file descriptor. At page 1858 line 61304, section readdir(), change: If a file is removed from or added to the directory after the most recent call to opendir() or rewinddir(), whether a subsequent call to readdir() returns an entry for that file is unspecified. to: If a directory entry is removed from or added to the directory after the most recent call to opendir() or rewinddir(), whether a subsequent call to readdir() on that directory stream returns that directory entry is unspecified. For all other directory entries in the directory that existed at the time the directory stream w
Minutes of the 2nd May 2024 Teleconference
All Enclosed are the minutes of yesterday’s teleconference regards Andrew -- Minutes of the 2nd May 2024 TeleconferenceAustin-1403 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 3rd May 2024 Attendees: Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE SA OR Eric Ackermann, CISPA Geoff Clare, The Open Group Andrew Josey, The Open Group Tom Thompson, IEEE Eric Blake, Red Hat, The Open Group OR Apologies Mark Ziegast, SHware Systems Dev * General news There will be no meeting on Monday May 6th. The IEEE Revcom committee meets on May 6 to consider approval of draft 4.1. After that we can moved forward to complete the frontmatter and proceed to publication, and the html conversion. The ISO/IEC ballot closes on June 28. Andrew noted that the company review of X/Open Curses Issue 8 has been announced and starts next week (informational only). Draft at: https://collaboration.opengroup.org/review-support/documents.php?action=show==56805 * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1817: lseek(2) - "size of a file" undefined OPEN https://austingroupbugs.net/view.php?id=1817 We continued on this item, notes are in the etherpad, and will continue on the item next time. Next Steps -- The next call is on: Mon 2024-05-06 NO MEETING Thu 2024-05-09 (WEBEX meeting - general bugs) Mon 2024-05-13 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 29th April 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew - Minutes of the 29th April 2024 TeleconferenceAustin-1402 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 1st May 2024 Attendees: Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE SA OR Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Eric Ackermann, CISPA Andrew Josey, The Open Group Tom Thompson, IEEE Apologies Mark Ziegast, SHware Systems Dev * General news There will be no meeting on Monday May 6th. The ISO/IEC ballot closes on June 28. The IEEE Revcom committee meets on May 6 to consider approval of draft 4.1. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1816: daylight, timezone, tzname do not work with location-based TZ Accepted as Marked https://austingroupbugs.net/view.php?id=1816 This item is tagged for TC1-2024. DESCRIPTION page 454 line 15841, change XSI to OB XSI. line 15843, change CX to OB CX. FUTURE DIRECTIONS page 454 line 15856, change "None" to: The variables daylight, timezone, and tzname are planned to be removed in a future version of this standard, as they have unspecified values unless the environment variable TZ is of the second format. daylight SYNOPSIS page 801 line 27445, change XSI to OB XSI. strptime DESCRIPTION page 2160 lines 70602-70606: add OB shading to "If this name matches ... shall be set to 0." timezone SYNOPSIS page 2279 line 74382, change XSI to OB XSI. Also remove the "()" after timezone in the page heading. tzset SYNOPSIS page 2310 line 75167: change XSI to OB XSI line 75169: change CX to OB CX line 75170: add CX margin marker tzset DESCRIPTION page 2310 lines 75175-75178 add OB margin marker and shading line 75175: Prepend "If the value of TZ is of the second format," line 75178: change "as described in XBD Chapter 8 (on page 167)" to "as described for the second TZ format in XBD Section 8.3 (on page 174)" line 75179: change XSI to OB XSI line 75179: Also prepend "If the value of TZ is of the second format," Line 75182: Append the following paragraph: [OB]If the value of TZ is not of the second format, the tzset() function shall set the array elements of the external variable tzname to point to unspecified string values[/OB] [OB XSI]and shall set the external variables daylight and timezone to unspecified values.[/OB XSI] line 75183: change XSI to OB XSI line 75199 (APPLICATION USAGE) Append the following paragraph: The values of the variables daylight, timezone, and tzname can only be relied upon to reflect the local timezone information if the environment variable TZ value is of the second format. Applications should use the tm_zone member of the tm structure instead of tzname and the tm_gmtoff member instead of timezone. When using tm_zone and tm_gmtoff there is no need for the information that is available in daylight. page 2311 line 75207 (tzset() FUTURE DIRECTIONS), change "None" to: The variables daylight, timezone, and tzname are planned to be removed in a future version of this standard, as they have unspecified values unless the environment variable TZ is of the second format. page 2311 line 75210 (tzset() SEE ALSO), change: XBD Chapter 8 (on page 167) to: XBD Section 8.3 (on page 174) Bug 1817: lseek(2) - "size of a file" undefined OPEN https://austingroupbugs.net/view.php?id=1817 We started on this item, and will continue on the item next time. Next Steps -- The next call is on: Thu 2024-05-02 (WEBEX meeting - general bugs) Mon 2024-05-06 NO MEETING Thu 2024-05-09 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 25th April 2024 Teleconference
All Enclosed are the minutes of the Thursday meeting this week regards Andrew Minutes of the 25th April 2024 TeleconferenceAustin-1401 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 26th April 2024 Attendees: Don Cragun, IEEE SA OR Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Eric Ackermann, CISPA Apologies Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev * General news A reminder that the next meeting will return to the regular webex bridge. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1816: daylight, timezone, tzname do not work with location-based TZ OPEN https://austingroupbugs.net/view.php?id=1816 The meeting was spent discussing this item, and will continue on the item next time. Notes are in the etherpad. Next Steps -- The next call is on: Mon 2024-04-29 (WEBEX meeting - general bugs) Thu 2024-05-02 (WEBEX meeting - general bugs) There is likely to be no meeting on May 6 as a UK Holiday. The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 18th April 2024 Teleconference
All
Enclosed are the minutes of today’s meeting.
A reminder there is no meeting on Monday 22nd, and that the meeting
on the 25th is using a different Webex bridge to normal.
regards
Andrew
--
Minutes of the 18th April 2024 TeleconferenceAustin-1400 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 18th April 2024
Attendees:
Don Cragun, IEEE SA OR
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Andrew Josey, The Open Group (partial)
Eric Blake, Red Hat, The Open Group OR
Geoff Clare, The Open Group
Eric Ackermann, CISPA
Tom Thompson, IEEE
Apologies
Mark Ziegast, SHware Systems Dev
* General news
A reminder there is no meeting on Monday 22nd, and that the meeting
on the 25th is using a different Webex bridge to normal.
* Current Business
1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797
We will continue this item next time that Paul is available (expected in April).
Bug 1813: generic xargs description cleanups Accepted as Marked
https://austingroupbugs.net/view.php?id=1813
This item is tagged for TC1-2024, and will require an interpretation timer to
start after approval of Issue 8.
Interpretation response:
The standard is unclear on this issue, and 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):
On page 3600 line 123176, change:
the application shall ensure that arguments in the standard
input are delimited by unquoted characters, unescaped
characters, or characters
to:
the application shall ensure that arguments in the standard
input are delimited by characters that are neither
quoted nor escaped, or by unescaped characters
After page 3600 line 123183, add two bullet items:
Quoting and escaping characters shall not be included in
the arguments passed to utility. Escaped characters
shall be included in the arguments.
It shall be an error if an attempt is made to quote a
character.
On page 3601 line 123231, change:
or {LINE_MAX} if there is no −s option
to:
or the default command line length if there is no −s option
On page 3601 line 123232, change:
The last iteration has fewer than number, but not zero, operands remaining.
to:
The last iteration has fewer than number operands remaining,
or zero arguments were read from standard input (and the -r
option is not specified).
On page 3602 line 123263, change:
The name of the utility to be invoked, found by search path using ...
to:
The name of the utility to be invoked. If the name does not
contain a character, the utility shall be found by
search path using ...
On page 3603 line 123302, change:
If the −t option is specified, the utility and its constructed
argument list shall be written to standard error, as it will
be invoked, prior to invocation.
to:
If the −t option is specified, the utility and its constructed
argument list, with a character preceding each argument
and a terminating , shall be written to standard error,
as it will be invoked, prior to invocation. Implementations may
insert quoting and escaping characters in the output produced
by -t such that the output (minus the utility name) can be
unambiguously used as input to a subsequent xargs command and
result in the same constructed argument list.
On page 3603 line 123304, change:
a prompt of the following format shall be written (in the POSIX
locale):
"?..."
at the end of the line of the output from −t.
to:
a prompt shall be written at the end of the line of the output
from −t. In the POSIX locale, the format of the prompt shall
be:
"?..."
Next Steps
--
The next call is on:
Mon 2024-04-22 NO MEETING
Thu 2024-04-25 (WEBEX meeting - general bugs) (note different webex)
Mon 2024-04-29 (WEBEX meeting - general bugs)
Apologies in advance:
2024-04-25 Nick Stoughton
The calls are for 90 minutes
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)
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to
Minutes of the 15th April 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week. Please note there is no meeting on Monday 22nd, and the 25th will use a different webex meeting number regards Andrew --- Minutes of the 15th April 2024 TeleconferenceAustin-1399 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 18th April 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group (partial) Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Eric Ackermann, CISPA Apologies Mark Ziegast, SHware Systems Dev * General news The IEEE approval meeting is due May 6. The ISO ballot has opened and completes at the end of June. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1810: fdopen() can only be used once per file descriptor Accepted as Marked https://austingroupbugs.net/view.php?id=1810 This item is tagged for TC1-2024. After page 899 line 30638, add to fclose() APPLICATION USAGE: If the file descriptor associated with the stream has already been closed, fclose() fails with an [EBADF] error (after it deallocates the stream). However, in the event that the same file descriptor number is allocated by some other operation (such as dup(), fopen(), open(), pipe(), socket(), and so forth), before fclose() is called, the fclose() call will close this newly allocated file descriptor instead. Therefore, applications which close the file descriptor before calling fclose() should ensure that they do not perform any file open operations in between closing the file descriptor and calling fclose(). This also applies in the event that two streams have the same associated file descriptor; calling fclose() on the first stream closes the file descriptor associated with both streams, and then calling fclose() on the second stream has the same risk described above. See also xref to P522, L18532 XSH 2.5.1 Interaction of File Descriptors and Standard I/O Streams. After page 918 line 31349, add to fdopen() APPLICATION USAGE: See also the APPLICATION USAGE for fclose(). Bug 1812: Support xargs -P 0 Accepted as Marked https://austingroupbugs.net/view.php?id=1812 This item is tagged for Issue 9. After making the page 3601 line 123232 change from bug 1801, change: If the value of maxprocs is non-positive, the behavior is unspecified. to: If the value of maxprocs is zero, the system heuristically attempts to minimize total runtime by executing multiple invocations of utility without waiting for previous executions to complete (e.g., by choosing the number of such invocations based on the number of available processors). If the value of maxprocs is negative, the behavior is unspecified. Bug 1813: generic xargs description cleanups OPEN https://austingroupbugs.net/view.php?id=1813 We will continue on this item next time. Next Steps -- The next call is on: Thu 2024-04-18 (WEBEX meeting - general bugs) Mon 2024-04-22 NO MEETING Thu 2024-04-25 (WEBEX meeting - general bugs) (note different webex) Apologies in advance: 2024-04-25 Nick Stoughton The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 11th April 2024 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew Minutes of the 11th April 2024 TeleconferenceAustin-1398 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 12th April 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group (partial) Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Apologies Eric Ackermann, CISPA Mark Ziegast, SHware Systems Dev * General news Action carried forward:Andrew took an action to reach out to Paul Eggert to find out when he can next attend. Andrew closed this action after the meeting. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1808: Add option -a to getconf utility Accepted as Marked https://austingroupbugs.net/view.php?id=1808 This item is tagged for issue9. After page 2831 line 93192 section getconf SYNOPSIS, add: getconf -a [-v specification] [pathname] After page 2831 line 93197 section getconf DESCRIPTION, add: If the -a option is specified, the getconf utility shall write to the standard output the names and values of all valid configuration variables; that is, every system_var operand and every path_var operand that the utility accepts, together with the values of the variables specified by those operands. For path_var operands the value written shall be the value of the variable for the path specified by the pathname operand, if present; if no pathname is provided, it is implementation-defined whether the value is for the current working directory (.) or the root directory (/). On page 2831 line 93204 section getconf OPTIONS, change: The following option shall be supported: to: The following options shall be supported: -a Write the names and values of all valid configuration variables. After page 2833 line 93307 section getconf STDOUT, add these new paragraphs: If the -a option is specified, the name of each valid configuration variable and information about the variable shall be written in the following format: "%s: %s\n", , where is the information string that would be written (without the terminating ) for the variable if specified as an operand, as described below. The remainder of this section describes the behavior if the -a option is not specified. On page 2834 line 93327 section getconf EXIT STATUS, change: The specified variable is valid and information about its current state was written successfully. to: The -a option was specified and the names of all valid configuration variables were written successfully together with information about each variable's current state, or the -a option was not specified, the specified variable is valid, and information about its current state was written successfully. On page 2834 line 9 section getconf APPLICATION USAGE, change: None. to: Since the value of a configuration variable obtained from confstr() may include characters, the output when the -a option is specified cannot be assumed to contain one name and value per line. Applications can use the presence of a at the end of the variable name as a means to distinguish names from parts of values that follow a ; however, it is possible (although unlikely) for a multi-line value to match this and it is recommended that applications needing to extract a list of valid variable names should confirm their validity by checking whether getconf accepts them as either a system_var or path_var operand. After page 2835 line 93364 section getconf RATIONALE, add a new paragraph: Historically the GNU implementation of getconf -a did not output a after each variable name, whereas other implementations did. The standard developers decided to require the in order to help applications and users distinguish variable names from parts of values that follow a . In some implementations the use of -v with -a was undocumented but supported; in others it was not supported, but it was felt to be a useful feature that would be simple to provide. Bug 1809: close() guidance to use fclose() should also discuss fdopen() Accepted as Marked https://austingroupbugs.net/view.php?id=1809 This item is tagged for TC1-2024. Change: An application that had used the stdio routine fopen() to open a file should use the corresponding fclose() routine rather than close(). Once a file is closed, the file descriptor no longer exists, since the integer corresponding to it no longer refers to a file. to: If the file descriptor is associated with a standard I/O stream (for example, if the file des
Minutes of the 8th April 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew Minutes of the 8th April 2024 TeleconferenceAustin-1397 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 10th April 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group (partial) Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Eric Ackermann, CISPA Apologies Mark Ziegast, SHware Systems Dev * General news As we had minimal attendance on April 4th that meeting was cancelled. The calls will continue on WEBEX for the moment. Andrew took an action to reach out to Paul Eggert to find out when he can next attend. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1808: Add option -a to getconf utility OPEN https://austingroupbugs.net/view.php?id=1808 We discussed this item. See the notes in the etherpad. We will continue on this item next time. Next Steps -- The next call is on: Thu 2024-04-11 (WEBEX meeting - general bugs) Mon 2024-04-15 (WEBEX meeting - general bugs) Apologies in advance: 2024-04-22 - 2024-04-25 Nick Stoughton The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 28th March 2024 Teleconference
All Enclosed are the minutes of the Thursday meeting last week regards Andrew --- Minutes of the 28th March 2024 TeleconferenceAustin-1396 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd April 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Apologies Eric Ackermann, CISPA Mark Ziegast, SHware Systemss Devs * General news We will not meet on April 1st. The calls will continue on WEBEX for the moment. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1807: Allow number of redirection open files to be up to OPEN_MAX / 2 - 1 Rejected https://austingroupbugs.net/view.php?id=1807 Making this change would actually have no effect on the highest fixed fd number a portable script can use in a redirection. This is because if the limit is OPEN_MAX/2 - 1, a portable script has to assume OPEN_MAX could have its lowest allowed value, _POSIX_OPEN_MAX, which happens to be 20, and 20/2 - 1 is 9. So a use such as "exec 200https://austingroupbugs.net/view.php?id=1808 We will continue this item next time Next Steps -- The next call is on: Thu 2024-04-04 (WEBEX meeting - general bugs) Mon 2024-04-08 (WEBEX meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 25th March 2024 Teleconference
All Enclosed are the minutes from the Monday meeting this week regards Andrew - Minutes of the 25th March 2024 TeleconferenceAustin-1395 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 28th March 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Geoff Clare, The Open Group Apologies Mark Ziegast, SHware Systemss Devs * General news A reminder that the US has switched to daylight saving time. The meetings until April will be one hour earlier for attendees in Europe. We will not meet on April 1st. The calls will continue on WEBEX for the moment. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). 1798: Must posix_getdents remember file offsets across exec? Accepted as marked https://austingroupbugs.net/view.php?id=1798 This item is tagged for TC1-2024 Proposed interpretation (review timer to start after approval of issue 8) using Draft 4.0 line numbers Interpretation response: The standard states that the posix_getdents() function starts reading at the current file offset in the open file description associated with fildes, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Elsewhere the standard makes allowances for implementations where directory streams are not implemented using a file descriptor, but this was not extended to the new posix_getdents() function when it was added. Notes to the Editor (not part of this interpretation): After page 920 line 31407 section fdopendir(), add a new paragraph: If the file descriptor specified by fd is associated with an open file description on which posix_getdents() has previously been used, or for which any associated file descriptor is already associated with a directory stream, the behavior is unspecified. After page 1567 line 52616 section posix_getdents(): The behavior is unspecified if lseek() is used to set the file offset to a value other than zero or a value returned by a previous call to lseek() on the same open file description. add these sentences: The behavior is unspecified if calls to posix_getdents() are made on different file descriptors that refer to the same open file description (for example, before and after a file descriptor is inherited across fork() or the exec family of functions, or is duplicated using dup() or fcntl()), unless lseek() is used to set the file offset to zero in between the calls to posix_getdents(). A single exception to this condition is that after a call to fork(), either the parent or child (but not both) can continue processing the directory using posix_getdents(). Likewise, the behavior is unspecified if in between two calls to posix_getdents() on one file descriptor, the file offset is altered by a call made on a different file descriptor that refers to the same open file description. At page 1568 line 52626 section posix_getdents(), change: If a sequence of calls to posix_getdents() is made that reads from offset zero to end-of-file and a file is removed from or added to the directory between the first and last of those calls, whether the sequence of calls returns an entry for that file is unspecified. to: If a sequence of calls to posix_getdents() is made that reads from offset zero to end-of-file and a directory entry is removed from or added to the directory between the first and last of those calls, whether the sequence of calls returns that directory entry is unspecified. After page 1571 line 52771 section posix_getdents(), add a new paragraph to RATIONALE: The restrictions on the use of different file descriptors that refer to the same open file description are needed in order to enable implementations where directory streams are not implemented using a file descriptor to maintain some internal state related to a particular file descriptor. At page 1858 line 61304, section readdir(), change: If a file is removed from or added to the directory after the most recent call to opendir() or rewinddir(), whether a subsequent call to readdir() returns an entry for that file is unspecified. to: If a directory entry is removed from or added to the directory after the most recent call to opendir() or rewinddir(), whether a subsequent call to readdir() on that directory stream returns that directory entry is unspecified. For all other directory entries in the directory that existed at the time the directory stream was opened or rewound and which have not be
Minutes of the 21st March 2024 Teleconference
hi all Enclosed are the minutes of the thursday meeting this week regards Andrew --- Minutes of the 21st March 2024 TeleconferenceAustin-1394 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 24th March 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Mark Ziegast, SHware Systemss Dev. Geoff Clare, The Open Group * General news The calls will continue on WEBEX for the moment. A reminder that the US has switched to daylight saving time. The meetings until April will be one hour earlier for attendees in Europe. We will not meet on April 1st. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available. Paul apologized for not making the 21st, and it now looks like it will be April before he can next join. 1798: Must posix_getdents remember file offsets across exec? Reopened https://austingroupbugs.net/view.php?id=1798 Although closed previously, we reopened the bug and continued the discussion from the previous meeting, and proposed a revised resolution (line numbers from draft 4): Proposed interpretation (review timer to start after approval of issue 8) ... Interpretation response: The standard states that the posix_getdents() function starts reading at the current file offset in the open file description associated with fildes, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Elsewhere the standard makes allowances for implementations where directory streams are not implemented using a file descriptor, but this was not extended to the new posix_getdents() function when it was added. Notes to the Editor (not part of this interpretation): After page 920 line 31407 section fdopendir(), add a new paragraph: If the file descriptor specified by fd is associated with an open file description on which posix_getdents() has previously been used, or for which any associated file descriptor is already associated with a directory stream, the behavior is unspecified. After page 1567 line 52616 section posix_getdents(): The behavior is unspecified if lseek() is used to set the file offset to a value other than zero or a value returned by a previous call to lseek() on the same open file description. add these sentences: The behavior is unspecified if calls to posix_getdents() are made on different file descriptors that refer to the same open file description (for example, before and after a file descriptor is inherited across fork() or the exec family of functions, or is duplicated using dup() or fcntl()), unless lseek() is used to set the file offset to zero in between the calls to posix_getdents(). A single exception to this condition is that after a call to fork(), either the parent or child (but not both) can continue processing the directory using posix_getdents(). Likewise, the behavior is unspecified if in between two calls to posix_getdents() on one file descriptor, the file offset is altered by a call made on a different file descriptor that refers to the same open file description. After page 1571 line 52771 section posix_getdents(), add a new paragraph to RATIONALE: The restrictions on the use of different file descriptors that refer to the same open file description are needed in order to enable implementations where directory streams are not implemented using a file descriptor to maintain some internal state related to a particular file descriptor. At page 1858 line 61312, section readdir(), change: If a file is removed from or added to the directory after the most recent call to opendir( ) or rewinddir( ), whether a subsequent call to readdir( ) returns an entry for that file is unspecified. to: If a file is removed from or added to the directory after the most recent call to opendir( ) or rewinddir( ), whether a subsequent call to readdir( ) on that directory stream returns an entry for that file is unspecified. For all other files in the directory that existed at the time the directory stream was opened and which have not been removed, successive calls to readdir( ) on that directory stream shall return an entry for each such file exactly once before reporting that the end of the directory has been reached, provided that there are no intervening calls to seekdir( ) and no unspecified behavior caused by opening a second directory stream on the same file description associated with the directory. For any such file that is renamed within the directory after the directory stream
Minutes of the 18th March 2024 Teleconference
All Enclosed are the minutes of the Monday meeting regards Andrew Minutes of the 18th March 2024 TeleconferenceAustin-1393 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th March 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Tom Thompson, IEEE (partial) Apologies Mark Ziegast, SHware Systemss Dev. Geoff Clare, The Open Group Paul Eggert * General news The calls will continue on WEBEX for the moment. A reminder that the US has switched to daylight saving time. The meetings until April will be one hour earlier for attendees in Europe. We will not meet on April 1st. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (March 21st). 1798: Must posix_getdents remember file offsets across exec? Accepted as Marked https://austingroupbugs.net/view.php?id=1798 Although closed previously, we continued the discussion from the previous meeting, and are yet to make a conclusion. This discussion took the whole meeting. Next Steps -- The next call is on: Thu 2024-03-21 (WEBEX meeting - general bugs) Mon 2024-03-25 (WEBEX meeting - general bugs) No meeting on April 1st. The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 14th March 2024 Teleconference
All Enclosed are the minutes of the Thursday meeting this week regards Andrew --- Minutes of the 14th March 2024 TeleconferenceAustin-1392 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 16th March 2024 Attendees: Don Cragun, IEEE SA OR Mark Ziegast, SHware Systemss Dev. Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Eric Ackermann, CISPA Apologies Paul Eggert * General news The Monday call will be on WEBEX. A reminder that the US has switched to daylight saving time. The meetings for the next three weeks will be one hour earlier for attendees in Europe. Draft 4.1 is ready to submit to IEEE RevCom and The Open Group Governing Board. After the meeting Andrew confirmed that this is now done. The draft will be considered at the May 6th IEEE RevCom meeting, and considered by The Open Group Governing Board in the March approvals (due by the end of March). * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (March 21st). 1798: Must posix_getdents remember file offsets across exec? Accepted as Marked https://austingroupbugs.net/view.php?id=1798 Although closed previously, we continued the discussion from the previous meeting, and are yet to make a conclusion. This discussion took the whole meeting. Next Steps -- The next call is on: Mon 2024-03-18 (WEBEX meeting - general bugs) Thu 2024-03-21 (WEBEX meeting - general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Apologies in advance: Geoff Clare 2024-03-18 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 11th March 2024 Teleconference
All Enclosed are the minutes of the Monday meeting regards Andrew -- Minutes of the 11th March 2024 TeleconferenceAustin-1391 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 13th March 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Eric Ackermann, CISPA Eric Blake, Red Hat, The Open Group OR Apologies Paul Eggert * General news A reminder that the US has switched to daylight saving time. The meetings for the next three weeks will be one hour earlier for attendees in Europe. The sanity review at The Open Group completed March 8th, no comments were received. The next stage is the Board review. The html conversion is still to be completed. Paul Eggert is unable to attend today. [After the meeting he confirmed next availability as March 20th] * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available. 1798: Must posix_getdents remember file offsets across exec? Accepted as Marked https://austingroupbugs.net/view.php?id=1798 Although closed previously, a discussion occurred during the meeting as follows: If an application does something like: dir1 = opendir(dirname); fd = dirfd(dir1); dirent1 = readdir(dir1); dir2 = fdopendir(fd); dirent2 = readdir(dir2); Does the standard require that dirent2 either report end-of-file or point to a directory entry that is not contained in the buffer used by dir1? And if both readdir(dir1) and readdir(dir2) continue to be used by a single thread and resinddir() is not called, are the directory entries returned by those readdir()s required to provide non-overlapping access to all of the directory entries in the directory named by dirname (subject to the constraints aboiut newluy added files might not be found by readir() on either stream and deleted files might be found by a readdir() on one of them after the file has been deleted)? Furthermore, if the readdir() calls are replaced by posix_getdents() calls using dup()ed file descriptors referring to the same file description, posix_getdents()s calls (using dirrerent buffers and different file descriptors) are required to fill the buffers with complete disjoint entries for the directory (with the same constraints about recently added and deleted files)? This discussion took the whole meeting. Next Steps -- The next call is on: Thu 2024-03-14 (Zoom meeting - general bugs) Mon 2024-03-18 (WEBEX meeting - general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Apologies in advance: Geoff Clare 2024-03-18 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 7th March 2024 Teleconference
All Enclosed are the minutes of the Thursday meeting this week. A reminder also that the US switches to daylight saving time on Sunday March 10th. The meetings for the next three weeks will be one hour earlier for attendees in Europe. regards Andrew --- Minutes of the 7th March 2024 TeleconferenceAustin-1390 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 9th March 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Paul Eggert Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Eric Ackermann, CISPA Tom Thompson, IEEE Eric Blake, Red Hat, The Open Group OR * General news Note that the US switches to daylight saving time on Sunday March 10th. The meetings for the next three weeks will be one hour earlier for attendees in Europe. We discussed the submission to the IEEE RevCom. The plan is to meet the next deadline which is March 26th. Andrew will prepare the elements for the submission during the next week. The sanity review at The Open Group completes March 8th, after which Board review is next. The html conversion is still to be completed. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We discussed this at length, and we will continue this item next time. Next Steps -- The next call is on: Mon 2024-03-11 (Zoom meeting - general bugs) Thu 2024-03-14 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 29th February 2024 Teleconference
All Enclosed are the minutes of the Thursday meeting this week. A reminder that there is no meeting on Monday March 4. regards Andrew -- Minutes of the 29th February 2024 TeleconferenceAustin-1389 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd March 2024 Attendees: Don Cragun, IEEE SA OR Mark Ziegast, SHware Systems Dev. Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, CISPA Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies: Andrew Josey, The Open Group * General news There is no meeting on Monday 2024-03-04. * Current Business Bug 1804: still some minor clarifications in the sed RE description Accepted as Marked https://austingroupbugs.net/view.php?id=1804 This item is tagged for TC1-2024 At page 3356 lines 114143 - 114145 change: The escape sequence '\n' shall match a embedded in the pattern space. A literal shall not be used in the RE of a context address or in the substitute function. to: The escape sequence followed by an 'n' shall match a embedded in the pattern space. The application shall ensure that an escaped literal is not used in the RE of a context address or the RE of an s command. At page 3360 line 114308 - 114320 change: Replace all occurrences of characters in string1 with the corresponding characters in string2. If a followed by an 'n' appear in string1 or string2, the two characters shall be handled as a single . If (after resolving any escape sequences) the numbers of characters in string1 and string2 are not equal, or if any of the characters in string1 appear more than once, the results are undefined. Any character other than or can be used instead of to delimit the strings. If the delimiter is not 'n', within string1 and string2, the delimiter itself can be used as a literal character if it is preceded by an unescaped . If a character is escaped by an immediately preceding unescaped character in string1 or string2, the two characters shall be treated as a single literal character. The meaning of an unescaped followed by any character that is not 'n', a , or the delimiter character is undefined. to: Replace all occurrences of characters in string1 with the corresponding characters in string2. Any character other than or can be used instead of to delimit the strings. If the delimiter is not 'n', within string1 and string2, the delimiter itself can be used as a literal character if it is preceded by an unescaped . If a character is escaped by a preceding unescaped character in string1 or string2, the two characters shall represent a single literal character. If an 'n' character is escaped by a preceding unescaped character in string1 or string2, the two characters shall represent a single literal . The meaning of an unescaped followed by any character that is not 'n', a , or the delimiter character is undefined. If (after resolving any escape sequences) the numbers of characters in string1 and string2 are not equal, or if any of the characters in string1 appear more than once, the results are undefined. 1798: Must posix_getdents remember file offsets across exec? Accepted as Marked https://austingroupbugs.net/view.php?id=1798 This item is tagged for TC1-2024. An interpretation timer should start after approval of Issue 8. Proposed interpretation (review timer to start after approval of issue 8) ... Interpretation response: The standard states that the posix_getdents() function starts reading at the current file offset in the open file description associated with fildes, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Elsewhere the standard makes allowances for implementations where directory streams are not implemented using a file descriptor, but this was not extended to the new posix_getdents() function when it was added. Notes to the Editor (not part of this interpretation): After page 920 line 31407 section fdopendir(), add a new paragraph: If the file descriptor specified by fd is associated with an open file description on which posix_getdents() has previously been used, the behavior is unspecified. After page 1567 line 52616 section posix_getdents(): The behavior is unspecified if lseek() is used to set the file offset to a value other than zero or a value returned by a previous call to lseek() on the same open file description. add these sentences: The behavior is unspecified if calls to posix_getdents() are made on different file descriptors that refer to the same open file description (for example, before and after a file descriptor is inherited across fork() or the exec family of functions, or is duplicated
Minutes of the 26th February 2024 Teleconference
All
Enclosed are the minutes of the Monday meeting this week
regards
Andrew
Minutes of the 26th February 2024 TeleconferenceAustin-1387 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 28th February 2024
Attendees:
Andrew Josey, The Open Group
Don Cragun, IEEE SA OR
Paul Eggert
Geoff Clare, The Open Group
Eric Ackermann, CISPA
Eric Blake, Red Hat, The Open Group OR
Mark Ziegast, SHware Systems Dev.
Apologies:
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
* General news
There is no meeting on Monday 2024-03-04.
The IEEE recirculation is still underway and ends on February 26
The Open Group Sanity review is underway and ends on March 8th.
After the meeting it was confirmed that the P1003.1 recirculation
ballot closed with a 100% approval rate and no new comments. We
are aiming to submit to IEEE and The Open Group in the second half
of March, noting that if before 26 March the draft would be placed
on the May RevCom agenda for consideration.
* Current Business
1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797
The meeting discussed this item at length.
Paul took an action to respond to the comment in the bug.
We will continue on this item next time.
1798: Must posix_getdents remember file offsets across exec? OPEN
https://austingroupbugs.net/view.php?id=1798
Notes are in the etherpad, this item to be continued.
Next Steps
--
The next call is on:
Mon 2024-03-04 NO meeting
Thu 2024-03-07 (Zoom meeting - general bugs)
The calls are for 90 minutes
There is no meeting 2024-03-04
Apologies in advance:
Andrew Josey, 2024-02-29
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)
----
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 22nd February 2024 Teleconference
All
Enclosed are the minutes of the thursday call this week.
A reminder that the call on Monday is using my WEBEX bridge.
There is also no meeting on the Monday after (March 4).
regards
Andrew
---
Minutes of the 22nd February 2024 TeleconferenceAustin-1387 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 24th February 2024
Attendees:
Don Cragun, IEEE SA OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Paul Eggert
Eric Blake, Red Hat, The Open Group OR
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Tom Thompson, IEEE
Mark Ziegast, SHware Systems Dev.
Apologies:
Eric Ackermann
* General news
The next meeting on the 26th February will be a webex meeting.
The IEEE recirculation is still underway and ends on February 26.
The Open Group Sanity review is underway and ends on March 8th.
* Current Business
1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797
The meeting discussed this item at length.
Paul took an action to submit an issue to start making daylight, timezone and
tzname obsolescent.
Completed after the meeting as issue 1816.
We will continue on this item next time.
1798: Must posix_getdents remember file offsets across exec? OPEN
https://austingroupbugs.net/view.php?id=1798
Notes are in the etherpad, this item to be continued.
Next Steps
--
The next call is on:
Mon 2024-02-26 (WEBEX meeting - general bugs)
Thu 2024-02-29 (Zoom meeting - general bugs)
The calls are for 90 minutes
There is no meeting 2024-03-04
Apologies in advance:
Nick Stoughton, 2024-02-26
Geoff Clare, 2024-03-04
Andrew Josey, 2024-02-29, 2024-03-04
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)
----
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 19th February 2024 Teleconference
All
Enclosed are the minutes from the Monday meeting this week
regards
Andrew
Minutes of the 19th February 2024 TeleconferenceAustin-1386 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 21st February 2024
Attendees:
Don Cragun, IEEE SA OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Mark Ziegast, SHware Systems Dev.
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Eric Blake, Red Hat, The Open Group OR
Apologies:
Tom Thompson
Eric Ackermann
* General news
The IEEE recirculation is underway and ends on February 26.
The Open Group Sanity review is underway and ends on March 8th.
* Current Business
1815: The _Fork() function is missing from the table of New Functions in Issue
8 Accepted as Marked
https://austingroupbugs.net/view.php?id=1815
This item is tagged for Issue 8
Add the _Fork() and posix_close() functions into the table ( SectionB.1.1
Change History ).
1814: `pthread_{spin,rwlock}_*` missing from discussion Rejected
https://austingroupbugs.net/view.php?id=1814
The functions mentioned in this bug are already included in the
table requiring synchronization. The paragraphs after the table
place additional syncronization requirements on the functions
discussed in those paragraphs. Therefore, this bug is rejected.
1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797
Paul Eggert will join the call on February 22nd.
1798: Must posix_getdents remember file offsets across exec? OPEN
https://austingroupbugs.net/view.php?id=1798
We discussed this item.
Notes are in the etherpad, this item to be continued.
Next Steps
--
The next call is on:
Thu 2024-02-22 (Zoom meeting - general bugs)
Mon 2024-02-26 (Zoom meeting - general bugs)
The calls are for 90 minutes
There is no meeting 2024-03-04
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)
----
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Re: Availability of 202x Draft 4.1
hi Corinna, all That appears to be an omission from the table in B.1.1 of the rationale volume. I have filed a bug report. We now have Draft 4.1 as a version to report bugs on in the Issue 8 drafts project. regards Andrew > On 16 Feb 2024, at 19:16, Corinna Vinschen via austin-group-l at The Open > Group wrote: > > Hi Andrew, > > I'm new to this, so bear with me if this isn't the right way to report > this small issue: > > On page 3732, "New features in Issue 8", the new _Fork() function > introduced on page 574 and described starting at page 983 seems to be > missing. Is that somehow deliberate? > > > Thanks, > Corinna > > On Feb 16 17:44, Andrew Josey via austin-group-l at The Open Group wrote: >> >> hi all, >> >> I'm pleased to announce the availability of draft 4.1 of the 202x revision >> of the standard. >> >> The draft can be obtained from the login page of the Austin Group at: >> https://www.opengroup.org/austin/login.html >> >> This is intended as the final draft, and is undergoing a 10 day recirculation >> at IEEE and the Sanity review at The Open Group. >> >> Since this is a recirculation draft, narrowing down rules apply and you may >> only comment on sections of the document that have changed as a result of >> the comments made against draft 4 >> which are a small number of editorials. >> >> A separate report is available with the draft. >> Any comments should be submitted to the Austin Group reflector. >> >> >> regards >> Andrew >> >> > Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Availability of 202x Draft 4.1
hi all, I'm pleased to announce the availability of draft 4.1 of the 202x revision of the standard. The draft can be obtained from the login page of the Austin Group at: https://www.opengroup.org/austin/login.html This is intended as the final draft, and is undergoing a 10 day recirculation at IEEE and the Sanity review at The Open Group. Since this is a recirculation draft, narrowing down rules apply and you may only comment on sections of the document that have changed as a result of the comments made against draft 4 which are a small number of editorials. A separate report is available with the draft. Any comments should be submitted to the Austin Group reflector. regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 15th February 2024 Teleconference
hi all Enclosed are the minutes from yesterday’s meeting regards Andrew -- Minutes of the 15th February 2024 TeleconferenceAustin-1385 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 16th February 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Eric Ackermann, CISPA Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. * General news We finalized the cover letter for Draft 4.1 and that will be released shortly for the Sanity review at The Open Group, and a 10 day recirculation at IEEE. We discussed the IEEE roster, which had triggered several emails to those attending the call. Andrew reported that he had commenced work on the html conversion process. The plan is to encapsulate this in a docker image, with the aim to integrate to the current gitlab project which creates the pdf. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 Andrew took an action to invite Paul Eggert to the call on February 22nd. Bug 1801: xargs: add -P optionAccepted as Marked https://austingroupbugs.net/view.php?id=1801 This item is tagged for Issue 9 . Change line 123162 from: [-s size] [utility [argument...]] to: [-P maxprocs] [-s size] [utility [argument...]] Add at line 123252: -P maxprocs Parallel mode: execute at most maxprocs invocations of utility concurrently. If the value of maxprocs is non-positive, the behavior is unspecified. Remove the FUTURE DIRECTIONS entry added by 0001811. Bug 1811: xargs: add -P option to FUTURE DIRECTIONS section Accepted https://austingroupbugs.net/view.php?id=1811 This item is tagged for TC1-2024. 1798: Must posix_getdents remember file offsets across exec? OPEN https://austingroupbugs.net/view.php?id=1798 Notes are in the etherpad from a previous meeting, this item to be continued. Next Steps -- The next call is on: Mon 2024-02-19 (Zoom meeting - general bugs) Thu 2024-02-22 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 12th February 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew Minutes of the 12th February 2024 TeleconferenceAustin-1384 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 13th February 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann Andrew Josey, The Open Group (Partial) Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group * General news The ballot on the proposed resolutions has been started at The Open Group and will complete on February 12th. Andrew will likely have to extend that ballot period due to the current return. Andrew has prepared the draft 4.1, and will release shortly. This will include details of the four editorials made, which will limit the scope for comments. We noted that the ISO/IEC ballot is now scheduled to start in 8 weeks time. Andrew confirmed he will submit the IEEE roster shortly. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We had received the reply from Paul Eggert (which is now copied into the Etherpad) We spent the meeting discussing this item and will continue next time. 1798: Must posix_getdents remember file offsets across exec? OPEN https://austingroupbugs.net/view.php?id=1798 Notes are in the etherpad from a previous meeting, this item to be continued. Next Steps -- The next call is on: Thu 2024-02-15 (Zoom meeting - general bugs) Mon 2024-02-19 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 8th February 2024 Teleconference
All Enclosed are the minutes from the Thursday meeting this week regards Andrew -- Minutes of the 8th February 2024 TeleconferenceAustin-1383 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 10th February 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Andrew Josey, The Open Group (partial) Eric Blake, Red Hat, The Open Group OR Eric Ackermann Mark Ziegast, SHware Systems Dev. Tom Thompson, IEEE * General news The ballot on the proposed resolutions has been started at The Open Group and will complete on February 12th. Andrew has prepared the draft 4.1, and plan to release after February 12. We will be issuing a 10-day recirculation at IEEE with draft 4.1. The scope of the comments will be the four editorials made. After the meeting we also received confirmation that the document format has been accepted for the ISO/IEC FDIS ballot which should to start soon. Andrew and Tom discussed the IEEE Roster with attendees, and we will be submitting the regular members of the call as the P1003.1 Roster (an IEEE procedural matter). * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 Open pending response to questions to Paul Eggert 1798: Must posix_getdents remember file offsets across exec? OPEN https://austingroupbugs.net/view.php?id=1798 Notes are in the etherpad, this item to be continued. 1799: endian.h unconditionally requires 64-bit integers Accepted as Marked https://austingroupbugs.net/view.php?id=1799 This item is tagged for tc1-2024 tag. An interpretation timer is to start after approval of issue 8. Once Issue 8 has been published, move the bug to the Issue 8 project and resolve it as follows (with page and line numbers updated if they change), and commence an interpretation review: Interpretation response: The standard states that uint64_t is required to be defined by but is optional in , and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Since implementations need to support uint64_t in order to implement , there is no point in having it be optionally defined in . For symmetry, int64_t should also be required in . Notes to the Editor (not part of this interpretation): On page 370 line 12957 section , after: int32_t add: int64_t On page 370 line 12960 section , after: uint32_t add: uint64_t Delete page 370 lines 12961-12975 Next Steps -- The next call is on: Mon 2024-02-12 (Zoom meeting - general bugs) Thu 2024-02-15 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 5th February 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew Minutes of the 5th February 2024 TeleconferenceAustin-1382 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 7th February 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann Apologies Mark Ziegast, SHware Systems Dev. Tom Thompson, IEEE * General news The ballot on the proposed resolutions has been started at The Open Group and will complete on February 12th. Andrew is preparing the draft 4.1. We will be issuing a 10-day recirculation at IEEE with draft 4.1. The scope of the comments will be the four editorials made. That will also fit well with the Sanity draft for The Open Group (part of their final process). Andrew reported during the meeting that the line number ballot at ISO/IEC has passed. We should expect the ISO/IEC FDIS ballot to start soon. * Current Business We closed bugs 1738 and 1742 properly (they had been left in the wrong state). 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We identified some questions to ask Paul Eggert and agreed to wait on the answers before proceeding. Eric B took an action to contact Paul. 1798: Must posix_getdents remember file offsets across exec? OPEN https://austingroupbugs.net/view.php?id=1798 We started on this item and will continue next time. Next Steps -- The next call is on: Thu 2024-02-08 (Zoom meeting - general bugs) Mon 2024-02-12 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 1st February 2024 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew --- Minutes of the 1st February 2024 TeleconferenceAustin-1380 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd February 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies Eric Ackermann Tom Thompson, IEEE * General news Draft 4 has ended its review at The Open Group and IEEE. There was a single editorial comment in The Open Group related to the abstract. At IEEE no new comments were received and two ballots changed to approve, resulting in 100% approval. We discussed comments from Patrick (IEEE editorial staff) about the changes for bugids 1795, 1796, 1800, and 1802. We have resolved all of these bugs with issue8 tags and will produce another draft. Andrew has asked Tom whether or not this draft should be sent out for a 10-day recirculation (even though we have 100% approval on the ballot on D4) or should ask RevCom to approve D4 and just submit the updated draft to IEEE to be published. After the meeting Tom has confirmed that he sees no issue with us creating a D4.1 with the editorials and doing a 10-day recirculation. That will also fit well with the Sanity draft for The Open Group (part of their final process). * Current Business We resolve the four editorial bugs on Draft 4. 1795: Field splitting rationale refers to non-existing rule number https://austingroupbugs.net/bug_view_page.php?bug_id=1795 Accepted, resolved, issue8 tag 1796: Table rendering problem https://austingroupbugs.net/bug_view_page.php?bug_id=1796 Accepted, resolved, issue8 tag 1800: be*toh() have no entries https://austingroupbugs.net/bug_view_page.php?bug_id=1800 Accepted as marked (bugnote:6644), resolved, issue8 tag 1802: Note missing paragraph break https://austingroupbugs.net/bug_view_page.php?bug_id=1802 Accepted, resolved, issue8 tag 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We continued on this item and will continue next time. We identified some questions to ask Paul Eggert. Next Steps -- The next call is on: Mon 2024-02-05 (Zoom meeting - general bugs) Thu 2024-02-08 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 29th January 2024 Teleconference
hi All Attached are the minutes of the Monday meeting this week regards Andrew --- Minutes of the 29th January 2024 TeleconferenceAustin-1380 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd February 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev Apologies Tom Thompson, IEEE * General news Draft 4 is still in review at The Open Group and IEEE. At IEEE no new comments were received and two ballots changed to approve, resulting in 100% approval. We discussed comments how to handle the editorials against draft four. Andrew took an action to followup with Tom. * Current Business Bug 1793: Streamline US-ASCII character set name https://austingroupbugs.net/bug_view_page.php?bug_id=1793 Accepted as marked, resolved, tc1-2024 tag. Proposed Changes Change the three occurrences of "US ASCII" to "ASCII". Add a definition to XBD chapter 3: 3.xxx ASCII The character encoding specified by the International Reference Version (IRV) of the ISO/IEC 646: 1991 standard. 1794: Please add tzalloc/tzfree and localtime_rz, mktime_z interfaces https://austingroupbugs.net/bug_view_page.php?bug_id=1794 Action: Eric to ask The Open Group if they are willing to sponsor these new interfaces. 1795: Field splitting rationale refers to non-existing rule number https://austingroupbugs.net/bug_view_page.php?bug_id=1795 To be accepted, resolved, issue8 tag (if Tom approves of editorial change) 1796: Table rendering problem https://austingroupbugs.net/bug_view_page.php?bug_id=1796 To be accepted, resolved, issue8 tag (if Tom approves of editorial change) 1800: be*toh() have no entries https://austingroupbugs.net/bug_view_page.php?bug_id=1800 To be accepted as marked (bugnote:6644), resolved, issue8 tag (if Tom approves of editorial change) 1802: Note missing paragraph break https://austingroupbugs.net/bug_view_page.php?bug_id=1802 To be accepted, resolved, issue8 tag (if Tom approves of editorial change) 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We started on this item and will continue next time. Next Steps -- The next call is on: Thu 2024-02-01 (Zoom meeting - general bugs) Mon 2024-02-05 (Zoom meeting - general bugs) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 25th January 2024 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew Minutes of the 25th January 2024 TeleconferenceAustin-1379 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 26th January 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann Geoff Clare, The Open Group Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR (joining late) Tom Thompson, IEEE * General news Draft 4 is still in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. * Current Business Bug 1793: Streamline US-ASCII character set name OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1793 We discussed this item at length and will continue next time. Notes are in the etherpad. Next Steps -- The next call is on: Mon 2024-01-29 (Zoom meeting - general bugs) Thu 2024-02-01 (Zoom meeting - general bugs) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Reminder: Review of 202x Draft 4 review draft closing soon
Dear all A gentle reminder that the review period for draft 4 closes next week (on January 31 2024). regards Andrew > On 19 Dec 2023, at 14:29, Andrew Josey via austin-group-l at The Open Group > wrote: > > > hi all, > > I'm pleased to announce the availability of the fourth draft of the 202x > revision of the standard. > > The draft can be obtained from the login page of the Austin Group at: > > https://www.opengroup.org/austin/login.html > > The Mantis project for reporting bugs for this draft has been setup and is > “Issue 8 drafts”, > select Product Version “Draft 4”. > > We have started The Open Group Company Review on this draft, and will be > starting the IEEE recirculation ballot on this draft shortly. The > review/ballot will close on January 31 2024. > > > I enclose the reviewers notes below. > regards > Andrew > > > 202x Draft 4 Reviewers Notes = Please Read > > These reviewers' notes accompany 202x Draft 4 dated December 2023. > > 202x Draft 4 is the second ballot draft of the POSIX.1-202x Revision (aka > IEEE P1003.1 Draft), and will be submitted for DIS ballot for ISO/IEC 9945. > This draft is also being submitted for The Open Group Company Review as The > Open Group Base Specifications, Issue 8 Draft. These notes should be read > prior to reviewing the document. > > IEEE, ISO/IEC balloting,The Open Group Company Review, and review by the > Austin Group Technical Reviewers will take place on this draft. This draft is > considered feature complete and is a release candidate for the final standard. > > The draft for the Austin Group and IEEE review has change markings to show > the changes applied since draft 3. > > All interested parties are invited to review these comments and submit > comments directly to the Austin Group. Please use the Mantis bug tracker at > https://austingroupbugs.net. The project in Mantis is "Issue 8 drafts". > Select "Draft 4". Further information on bugreporting against these documents > can be found at https://www.opengroup.org/austin/Mantis_Reporting_Help.html. > > In order to submit comments, you need to have a Mantis account. If you do not > have a Mantis account you will need to request one by contacting Andrew Josey > for assistance. > > Since this is a recirculation draft, narrowing down rules apply and you may > only comment on sections of the document that have changed as a result of the > comments made against draft 3. Changes are marked with change bars. > > A separate report is available in the Austin Group document register > (Austin/1371) detailing the bug reports leading to changes in Draft 4. > > Background information on the Issue 8 Project > > Please see the following documents from the Document register > (http:/www.opengroup.org/austin/docreg.html) for details of the Issue 8 > project. > > • Austin/936 (PDF) — PAR for P1003.1-202x Revision (Submitted June 21 > 2019) , revised November 2023, see Austin/1360 > • Austin/937r1 — Final PASC PMC Criteria for P1003.1-202x Revision > > > Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 22nd January 2024 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew --- Minutes of the 22nd January 2024 TeleconferenceAustin-1378 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 24th January 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Dev. Eric Ackermann Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Levon Tumanyan Tom Thompson, IEEE Apologies Geoff Clare, The Open Group * General news Draft 4 is still in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. * Current Business Bug 1789: if command name contains slash, it cannot be arg0 for execl() Accepted as Marked https://austingroupbugs.net/view.php?id=1789 We revisited this based on comments received. Note: 0006621 has been updated as suggested by Note: 0006631 Bug 1791: tr: clarify encdings of non-characters bytes and proper encodings of the NUL byte and Rejected https://austingroupbugs.net/bug_view_page.php?bug_id=1791 Rejected, closed. NUL is not a special case; NUL is a character in every locale. The standard says that the strings specified by string1 and string2 contain characters. A single character in those strings may be represented by one or more adjacent octal sequences that represent individual bytes of a multi-byte character. The notes in the APPLICATION USAGE and in the RATIONALE specify that tr -d '\000' must remove NUL characters from the input stream. This would also work with tr -d '\0' and tr -d '\00'. But if one wanted to remove NUL characters and the character '1', one would have to use tr -d '\0001' (or put the '1' before the octal escape sequence for the NUL character, e.g. tr -d '1\0'); not tr -d '\01' or tr -d '\001'. Therefore, this bug is rejected. We started on this item and will continue on the next call. Bug 1792: Example 7 needs to use find's -H option Accepted as Marked https://austingroupbugs.net/bug_view_page.php?bug_id=1792 This item is tagged for TC1-2024. Make the changes suggested, including the addition of "provided both file1 and file2 are accessible" (add after example). Bug 1793: Streamline US-ASCII character set name OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1793 We will start on this item next time. Next Steps -- The next call is on: Thu 2024-01-25 (Zoom meeting - general bugs) Mon 2024-01-29 (Zoom meeting - general bugs) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 18th January 2024 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew - Minutes of the 18th January 2024 TeleconferenceAustin-1377 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 19th January 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Dev. Eric Ackermann Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies Tom Thompson, IEEE Geoff Clare, The Open Group * General news Draft 4 is still in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. * Current Business Bug 1789: if command name contains slash, it cannot be arg0 for execl() Accepted as Marked https://austingroupbugs.net/view.php?id=1789 We revisited this based on comments received. Note: 0006621 has been updated to break the run-on sentence as suggested. Bug 1790: More info on *ALT* constants Accepted as Marked https://austingroupbugs.net/bug_view_page.php?bug_id=1790 This item is tagged for TC1-2024 (D4 page and line numbers.) Add to Application Usage, page 277 after line 9645: For languages having both a genitive (when used with a day number) and a nominative (no day number) case, the "alternative" month names described here are for use when a nominative case is required, see XREF 7.3.5.1 LC_TIME Locale Definition. Bug 1791: tr: clarify encdings of non-characters bytes and proper encodings of the NUL byte and OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1791 We started on this item and will continue on the next call. Next Steps -- The next call is on: Mon 2024-01-22 (Zoom meeting - general bugs) Thu 2024-01-25 (Zoom meeting - general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Apologies in Advance: Geoff Clare, 2024-01-22 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 15th January 2024 Teleconference
All
Enclosed are the minutes of the Monday call this week
regards
Andrew
--
Minutes of the 15th January 2024 TeleconferenceAustin-1376 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 17th January 2024
Attendees:
Don Cragun, IEEE SA OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Mark Ziegast, SHware Systems Dev.
Eric Ackermann
Andrew Josey, The Open Group
Eric Blake, Red Hat, The Open Group OR
Levon Tumanyan
Apologies
Tom Thompson, IEEE
Geoff Clare, The Open Group
* General news
Draft 4 is still in review at The Open Group and IEEE,
with the review closing on January 31 2024. No comments
have been received as yet.
We discussed when the ISO/IEC draft is due to go to ballot.
Andrew and Nick noted that is expected to be after the
ballot on approving the use of line numbers concludes and that they would
check with Bill Ash.
* Current Business
Bug 1789: if command name contains slash, it cannot be arg0 for execl()
Accepted as Marked
https://austingroupbugs.net/view.php?id=1789
On page 865 line 29495, 29499 change: (D4 p877 line 29519)
... should point to a filename string that is associated with
the process being started by one of the exec functions.
to:
... should point to a string that is associated with the with
the filename of the process being started by one of the exec
functions.
and add to Application Usage, page 872 after line 29773: (D4 p874 line 29796)
The string in arg0 or argv[0] is typically the basename of the
path of the file being executed. However, there is no requirement
in this standard that this is so, and the program executed will
see this string in the first element of the argv[] array passed
to its main() function, and may alter its functionality based
on this.
On page 872 Rationale, line 29785, change (D4 p874 line 29808)
... the first argument be a filename string associated with the
process being started. Although some existing applications pass
a pathname rather than a filename string in some circumstances,
a filename string is more generally useful, since the common
usage of argv[0] is in printing diagnostics. In some cases the
filename passed is not the actual filename of the file; for
example, many implementations of the login utility use a
convention of prefixing a ('-') to the actual
filename, which indicates to the command interpreter being
invoked that it is a ``login shell’’.
to:
... the first argument be simply a string associated with the
filename of the process being started. Most applications pass
a filename string or a pathname string, a filename string is
more generally useful, since the common usage of argv[0] is in
printing diagnostics. In some cases the filename in the string
passed is not the actual filename of the file; for example,
many implementations of the login utility use a convention of
prefixing a ('-') to the actual filename, which
indicates to the command interpreter being invoked that it is
a ``login shell’’.
Bug 1790: More info on *ALT* constants
https://austingroupbugs.net/bug_view_page.php?bug_id=1790
We will continue on this item on the next call.
Next Steps
--
The next call is on:
Thu 2024-01-18 (Zoom meeting - general bugs)
Mon 2024-01-22 (Zoom meeting - general bugs)
The calls are for 90 minutes
Calls are anchored on US time. (8am Pacific)
Apologies in Advance:
Geoff Clare, 2024-01-15 to 2024-01-22 inclusive
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)
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 11th January 2024 Teleconference
All Enclosed are the minutes from the thursday meeting this week regards Andrew -- Minutes of the 11th January 2024 TeleconferenceAustin-1375 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 12th January 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group Eric Ackermann Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Levon Tumanyan Apologies Tom Thompson, IEEE * General news Draft 4 is still in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. Andrew and Don reported they had attended the quarterly IEEE MSC meeting, and that it had confirmed Don as the IEEE SA OR. * Current Business Bug 1788: The meaning of "Daylight Saving Time" should be clarified Accepted as Marked https://austingroupbugs.net/view.php?id=1788 This item is marked for TC1-2024. It was noted that the resolution of this bug should just address the missing definitions. Any additional changes related to tzname[] etc. should be the subject of a separate bug. Add the following to the definitions in XBD chapter 3 putting them in alphabetical order and renumbering moved definitions. 3.xxx Daylight Saving Time (DST) The time according to a location's law or practice, when adjusted as necessary from standard time. The adjustment can be positive or negative, and the amount of adjustment can vary depending on the date and time; the adjustment can even be zero, although this is not common practice. Note: timezone information can be supplied via the TZ environment variable, which is defined in detail in [xref to XBD 8.3]. See also [xref to 3.yyy Standard Time]. 3.yyy Standard Time The time according to a location's law or practice, unadjusted for Daylight Saving Time. Note: timezone information can be supplied via the TZ environment variable, which is defined in detail in [xref to XBD 8.3]. See also [xref to 3.xxx Daylight Saving Time]. Bug 1789: if command name contains slash, it cannot be arg0 for execl() OPEN https://austingroupbugs.net/view.php?id=1789 We started this item and notes are in the etherpad. We will continue on this on the next call. Next Steps -- The next call is on: Mon 2024-01-15 (Zoom meeting - general bugs) Thu 2024-01-18 (Zoom meeting - general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Apologies in Advance: Geoff Clare, 2024-01-15 to 2024-01-22 inclusive 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 8th January 2024 Teleconference
All Enclosed are the minutes from the Monday meeting this week regards Andrew Minutes of the 8th January 2024 TeleconferenceAustin-1374 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 8th January 2024 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies Eric Ackermann Tom Thompson, IEEE * General news Draft 4 is currently in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. An updated draft has been submitted to ISO/IEC addressing minor editorial comments received. * Current Business Bug 1788: The meaning of "Daylight Saving Time" should be clarified OPEN https://austingroupbugs.net/view.php?id=1788 We continued this item and notes are in the etherpad. We will continue on this on the next call. Next Steps -- The next call is on: Thu 2024-01-11 (Zoom meeting - general bugs) Mon 2024-01-15 (Zoom meeting - general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Apologies in Advance: Geoff Clare, 2024-01-15 to 2024-01-22 inclusive 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Re: IANA TZ / NerBSD TZ: tzalloc/tzfree and localtime_rz, mktime_z
> On 5 Jan 2024, at 05:12, Robert Elz via austin-group-l at The Open Group > wrote: > >Date:Thu, 04 Jan 2024 23:24:26 +0100 >From:Steffen Nurpmeso >Message-ID: <20240104222426.ai7_3Mvo@steffen%sdaoden.eu> > > | I was hoping for the draft; the selection list does not offer > | anything but ..TC2 and it. > > If you want, you can submit a bug now, using any base standard > that is in some way still current. It just won't get processed > at all (beyond random notes being added) until the next standard > is being worked on, so submitting now is kind of pointless. > Not necessarily, Austin/SD6 (https://www.opengroup.org/austin/docs/austin_sd6.txt) lays out the Committee Maintenance Procedures for the Approved Standard, and there is a section on new work items. So a proposal could advance that way, and lead to a separate standard adopted by one of the sponsoring organizations, and later adopted to issue 9. Over the years we have progressed a number of new API sets this way, before they went into the main standard ( the Extended API Sets Parts 1..4, and the Additional APIs for the Base Specifications Issue 8 Parts 1 and 2). regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 4th January 2024 Teleconference
hi All Happy New Year! Attached are the minutes of our first meeting of the year regards Andrew - Minutes of the 4th January 2024 TeleconferenceAustin-1373 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 5th January 2024 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies Tom Thompson, IEEE * General news Draft 4 is now in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. The draft was submitted to ISO/IEC, and after the meeting some comments have been received from the ISO editors that need to be addressed, to set the document on A4 (from US Letter), also to remove any reviewers notes (there is on in §1.6 Terminology). Andrew completed the action to issue a status report (Austin/1372). Andrew reported he has been added to the IEEE CS MSC mailing list (the successor to the PASC). A meeting is scheduled for January 9th. An item for the meeting is to confirm that Don will continue as the IEEE SA representative to the Austin Group. * Current Business Bug 1785: Conflict in specification of processing of declaration utilities Accepted as Marked https://austingroupbugs.net/view.php?id=1785 This item is tagged for TC1-2024. On page 2483 line 80766 section 2.9.1.1, change: The first word (if any) that is not a variable assignment or redirection shall be expanded. If any fields remain following its expansion, the first field shall be considered the command name. If no fields remain, the next word (if any) shall be expanded, and so on, until a command name is found or no words remain. If there is a command name and it is recognized as a declaration utility, then any remaining words after the word that expanded to produce the command name, that would be recognized as a variable assignment in isolation, shall be expanded as a variable assignment (tilde expansion after the first and after any unquoted , parameter expansion, command substitution, arithmetic expansion, and quote removal, but no field splitting or pathname expansion); while remaining words that would not be a variable assignment in isolation shall be subject to regular expansion (tilde expansion for only a leading , parameter expansion, command substitution, arithmetic expansion, field splitting, pathname expansion, and quote removal). For all other command names, words after the word that produced the command name shall be subject only to regular expansion. All fields resulting from the expansion of the word that produced the command name and the subsequent words, except for the field containing the command name, shall be the arguments for the command. to: The first word (if any) that is not a variable assignment or redirection, and any subsequent words, shall be processed as follows: The first word may be matched lexically against the names of declaration utilities. The first word shall be expanded. If any fields remain following expansion of the first word, the first field shall be considered the command name. If no fields remain, the next word (if any) shall be expanded, and so on, until a command name is found or no words remain. If the above optional matching against the names of declaration utilities was not performed and there is a command name, the command name shall be matched lexically against the names of declaration utilities. If whichever of the matching operations that was performed produced a successful match, any remaining words after the word that expanded to produce the command name, that would be recognized as a variable assignment in isolation, shall be expanded as a variable assignment (tilde expansion after the first and after any unquoted , parameter expansion, command substitution, arithmetic expansion, and quote removal, but no field splitting or pathname expansion); while remaining words that would not be a variable assignment in isolation shall be subject to regular expansion (tilde expansion for only a leading , parameter expansion, command substitution, arithmetic expansion, field splitting, pathname expansion, and quote removal). If the matching operation did not produce a successful match, words after the word that produced the command name shall be subject only to regular expansion. All fields resulting from the expansion of the word that produced the command name and the subsequent words, except for the field containing the command name, shall
Austin Group Status/1003.1 Status Report
All Enclosed is a status report for December 2023 regards Andrew Austin Group Status/1003.1 Status ReportAustin-1372 Page 1 of 1 Submitted by Andrew Josey, The Open Group December 19, 2023 The Austin Common Standards Revision Group (CSRG) is a joint technical working group established to develop and maintain the core open systems interfaces that are the POSIX® 1003.1 (and former 1003.2) standards, ISO/IEC 9945, and the core of the Single UNIX Specification. The working group brings together the technical experts from ISO JTC1, IEEE and The Open Group. The latest revision to the 1003.1 standard was published in January 2018. The current activities are development of a major revision, as well as maintenance of the standard, and managing defect reports. Draft 4 of the revision was made available in December 2023. The draft can be obtained from the login page of the Austin Group at: https://www.opengroup.org/austin/login.html This draft is being submitted for The Open Group Company Review, and the IEEE recirculation ballot. The review/ballot at The Open Group and IEEE will close on January 31 2024. The draft will also be submitted to ISO/IEC for DIS ballot. The Mantis project for reporting bugs for this draft is “Issue 8 drafts”, select Product Version “Draft 4”. Since this is a recirculation draft, narrowing down rules apply and only comments on sections of the document that have changed as a result of the comments made against draft 3 will be accepted. Changes are marked with change bars. A separate report is available in the Austin Group document register (Austin/1371) detailing the bug reports leading to changes in Draft 4. The group meets regularly by teleconference to consider defect reports and issues on the current approved standard. Minutes are kept in the Document register at http://www.opengroup.org/austin/docreg.html . The group uses an online defect reporting system for maintenance of the standard, see http://austingroupbugs.net The next working group meeting is listed at http://www.opengroup.org/austin/ in the events diary. Further information on the Austin Group can be obtained at http://www.opengroup.org/austin/faq.html Respectfully submitted, Andrew Josey, The Open Group, 1003.1 Chair Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Availability of 202x Draft 4 review draft
hi all, I'm pleased to announce the availability of the fourth draft of the 202x revision of the standard. The draft can be obtained from the login page of the Austin Group at: https://www.opengroup.org/austin/login.html The Mantis project for reporting bugs for this draft has been setup and is “Issue 8 drafts”, select Product Version “Draft 4”. We have started The Open Group Company Review on this draft, and will be starting the IEEE recirculation ballot on this draft shortly. The review/ballot will close on January 31 2024. I enclose the reviewers notes below. regards Andrew 202x Draft 4 Reviewers Notes = Please Read These reviewers' notes accompany 202x Draft 4 dated December 2023. 202x Draft 4 is the second ballot draft of the POSIX.1-202x Revision (aka IEEE P1003.1 Draft), and will be submitted for DIS ballot for ISO/IEC 9945. This draft is also being submitted for The Open Group Company Review as The Open Group Base Specifications, Issue 8 Draft. These notes should be read prior to reviewing the document. IEEE, ISO/IEC balloting,The Open Group Company Review, and review by the Austin Group Technical Reviewers will take place on this draft. This draft is considered feature complete and is a release candidate for the final standard. The draft for the Austin Group and IEEE review has change markings to show the changes applied since draft 3. All interested parties are invited to review these comments and submit comments directly to the Austin Group. Please use the Mantis bug tracker at https://austingroupbugs.net. The project in Mantis is "Issue 8 drafts". Select "Draft 4". Further information on bugreporting against these documents can be found at https://www.opengroup.org/austin/Mantis_Reporting_Help.html. In order to submit comments, you need to have a Mantis account. If you do not have a Mantis account you will need to request one by contacting Andrew Josey for assistance. Since this is a recirculation draft, narrowing down rules apply and you may only comment on sections of the document that have changed as a result of the comments made against draft 3. Changes are marked with change bars. A separate report is available in the Austin Group document register (Austin/1371) detailing the bug reports leading to changes in Draft 4. Background information on the Issue 8 Project Please see the following documents from the Document register (http:/www.opengroup.org/austin/docreg.html) for details of the Issue 8 project. • Austin/936 (PDF) — PAR for P1003.1-202x Revision (Submitted June 21 2019) , revised November 2023, see Austin/1360 • Austin/937r1 — Final PASC PMC Criteria for P1003.1-202x Revision ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 18th December 2023 Teleconference
All Enclosed are the minutes from yesterday’s meeting. A reminder that the next meeting is on January 4th regards Andrew --- Minutes of the 18th December 2023 TeleconferenceAustin-1370 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 19th December 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Eric Ackermann Andrew Josey, The Open Group Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Tom Thompson, IEEE Ahmet Acar * General news We reviewed the actions from the previous meeting. Andrew and Geoff have prepared the draft for release. We need to finalize the notes to reviewers, and generate a report of all changes post draft 3 (to be Austin/1371). The draft has been issued to The Open Group company review as planned, and will be issued on Tuesday 19th to the Austin Group, then submitted to IEEE. A number of questions have been sent regarding document requirements for the ISO DIS ballot. The following action is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report (to be done when D4 is available) * Current Business Bug 1785: Conflict in specification of processing of declaration utilities OPEN https://austingroupbugs.net/view.php?id=1785 We discussed this item at length. Notes are in the etherpad. We will continue on this on the next call. Next Steps -- There will now be a break until January 4 2024. The next call is on: Thu 2024-01-04 (Zoom meeting - general bugs/ballot resolution) Mon 2024-01-08 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 14th December 2023 Teleconference
hi all Enclosed are the minutes of the thursday meeting this week regards Andrew -- Minutes of the 14th December 2023 TeleconferenceAustin-1369 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 16th December 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Eric Ackermann Andrew Josey, The Open Group Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Apologies Tom Thompson, IEEE * General news We reviewed the actions from the previous meeting. The draft frontmatter has been reviewed by IEEE staff. to the IEEE staff to check. We will be able to generate a report of all changes made post draft 3, which we will make available as part of the comments package back to IEEE and ISO/IEC. We plan to make the draft on Monday 18th, just in time to start The Open Group company review. We will then also submit for the IEEE ballot recirculation during the week. We will also prepare the feedback to ISO/IEC. The following action is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report (to be done when D4 is available) We discussed setting up a new tag for Issue 8 TC1 and confirmed that this is a straightforward task, we just need to agree the tag when we use it first. * Current Business Bug 1784: getopts specification needs fixing (multiple issues) Accepted as Marked https://austingroupbugs.net/view.php?id=1784 Comments had been received on the resolution from the last call. These were discussed and the bug note updated, see the bug note for details https://austingroupbugs.net/view.php?id=1784#c6600 Note: 0006600 has been updated in place to address issues discussed in Note: 0006602-Note: 0006604 and Note: 0006606-Note: 0006608. It is proposed to merge the resolution to draft 4. Next Steps -- The next call is on: Mon 2023-12-18 (Zoom meeting - general bugs/ballot resolution) There will then be a break until January 4 2024. Thu 2024-01-04 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 11th December 2023 Teleconference
All Enclosed are the minutes from yesterday’s call regards Andrew --- Minutes of the 11th December 2023 TeleconferenceAustin-1368 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 12th December 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Eric Ackermann Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Ahmet Acar Apologies Tom Thompson, IEEE * General news We reviewed the actions from the previous meeting. Andrew confirmed he has update the comment dispositions to Revised at IEEE and is continuing with preparation. Andrew has prepared revised draft frontmatter taking into account the change of the Computer Society committee. He has submitted this to the IEEE staff to check. Andrew has prepared a disposition of the ISO comments, with the change from what was prepared before to put a revised response for US-001 which is about the format of the document Andrew has closed out bug report 1738. After the meeting Andrew also closed out bug 1742, he will ensure that in the response to the ISO/IEC ballot comments that we confirm the draft has been synchronized. The following action is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report (to be done when D4 is available) We noted that D4 is intended to be a stable draft, so if we feel any of the last bugs are controversial we would be best to hold them for TC1. * Current Business We discussed a mailing list item about the return value for ed (austin-group-l:archive/latest/36799). Eric B took an action to respond to Andrew Moore (see guidance in the etherpad for details). Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1784: getopts specification needs fixing (multiple issues) Accepted as Marked https://austingroupbugs.net/view.php?id=1784 On P67, L2057-2058 (XBD 3.244 Option-Argument definition) change: A parameter that follows certain options. In some cases an option-argument is included within the same argument string as the option—in most cases it is the next argument. to: A parameter that follows certain options. In some cases an option-argument immediately follows the option character within the same argument string as the option; otherwise the option-argument is the next argument string. On page 2995 line 98801 change: getopts optstring name [arg...] to: getopts optstring name [param...] And globally rename s/arg/param/ elsewhere in the remainder of the getopts page. On page 2995 lines 98806-98808 Change: Each time it is invoked, the getopts utility shall place the value of the next option in the shell variable specified by the name operand and the index of the next argument to be processed in the shell variable OPTIND. Whenever the shell is invoked, OPTIND shall be initialized to 1. to: When the shell is first invoked, the shell variable OPTIND shall be initialized to 1. Each time getopts is invoked, it shall place the value of the next option found in the parameter list in the shell variable specified by the name operand and the shell variable OPTIND shall be set as follows: When getopts successfully parses an option that takes an option-argument (that is, a character followed by in optstring, and exit status is 0), the value of OPTIND shall be the integer index of the next parameter to be searched for an option character. Index 1 identifies the first element of the parameter list. When getopts reports end of options (that is, when exit status is 1), the value of OPTIND shall be the integer index of the next element of the parameter list (if any; see below). In all other cases, the value of OPTIND is unspecified, but shall encode the information needed for the next invocation of getopts to resume parsing options after the option just parsed Replace Lines 98830-98835 with: When the end of options is encountered, the getopts utility shall exit with a return value of one; the shell variable OPTIND shall be set to the index of the argument containing the first operand in the parameter list, or the value 1 plus the number of elements in the parameter list if there are no operands in the parameter list; the name variable shall be set to the character. Any of the following shall identify the end of options: the first "--" element of the parameter list that is not an option-argument, finding an element of the parameter list that is not an option-argument and does
Fwd: Bug 1778 in Minutes of the 27th November 2023 Teleconference
hi all This did not make it to the list (sender not recognized), so forwarding > Begin forwarded message: > > From: Brian Inglis > Subject: Re: Bug 1778 in Minutes of the 27th November 2023 Teleconference > Date: 3 December 2023 at 15:33:31 GMT > > > "Bug 1778: The read utility needs field splitting updates/corrections) and a > little more) Accepted as Marked > https://austingroupbugs.net/view.php?id=1778 > > On page 3291 line 111859 section read, change: >By default, unless the -r option is specified, shall >act as an escape character. An unescaped shall >preserve the literal value of the following character, with the >exception of ... > > to: >If the -r option is not specified, shall act as an >escape character. An unescaped shall preserve the >literal value of a following and shall prevent a >following byte (if any) from being used to split fields, with >the exception of ..." > > In edited post-d3 line 111861: > >literal value of a following *and* shall prevent a > > should this *and* be /or/? > > Using *and* seems to imply that you would need to specify: > > \\ > > to use it, while /or/ should more clearly indicate the intended alternatives: > > \\ -> \ > \ -> > \ > > > -- > Take care. Thanks, Brian Inglis Calgary, Alberta, Canada > Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org <mailto:a.jo...@opengroup.org> Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy <http://www.opengroup.org/privacy>. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481 <https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481>
Minutes of the 7th December 2023 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew Minutes of the 7th December 2023 TeleconferenceAustin-1367 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 8th December 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Eric Ackermann Andrew Josey, The Open Group Geoff Clare, The Open Group Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. Ahmet Acar * General news We discussed the draft disposition for IEEE ballot comments. It was agreed that it was best to set each disposition to "revised", so we can then point into the Mantis bug report for details. If we put "accept" then the further details column is supposed to be empty. Andrew will update the comment dispositions at IEEE and continue with preparation. We discussed the period for the ballot, and noted that a long ballot is planned to run up until Jan 31 2024. We discussed the next draft, and noted for IEEE it must be change marked. Don noted that with the change of the Computer Society committee that the front matter will need to change. Andrew will prepare a draft frontmatter. Andrew reported that Bill Ash of NCITS has been in touch enquiring when the next draft would be available so that is timely. Andrew will need to prepare a disposition of the ISO comments. Andrew will need to close out Bug reports 1738 and 1742 The following action is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1784: getopts specification needs fixing (multiple issues) OPEN https://austingroupbugs.net/view.php?id=1784 We continued on this item and notes were made in the etherpad. We will continue next time. Next Steps -- We will continue on bug 1784 next time. The next call is on: Mon 2023-12-11 (Zoom meeting - general bugs/ballot resolution) Thu 2023-12-14 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 4th December 2023 Teleconference
All Enclosed are the minutes from yesterdays call regards Andrew - Minutes of the 4th December 2023 TeleconferenceAustin-1366 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 5th December 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Eric Ackermann Ahmet Acar Apologies: Geoff Clare, The Open Group * General news The following action is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1784: getopts specification needs fixing (multiple issues) OPEN https://austingroupbugs.net/view.php?id=1784 We continued on this item and notes were made in the etherpad. We will continue next time. Next Steps -- We will continue on bug 1784 next time. The next call is on: Thu 2023-12-07 (Zoom meeting - general bugs/ballot resolution) Mon 2023-12-11 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Apologies in advance: Geoff Clare, 2023-12-07 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 30th November 2023 Teleconference
All Enclosed are the minutes of the Thursday call this week regards Andrew Minutes of the 30th November 2023 TeleconferenceAustin-1365 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd December 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies Geoff Clare, The Open Group Andrew Josey, The Open Group * General news The following action is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1787: strcpy summary says it returns a pointer to the end of the result Accepted as Marked https://austingroupbugs.net/view.php?id=1787 This item is tagged for TC3-2008. It was noted that in Issue 6 and earlier the NAME section was simply: strcpy - copy a string and the problem introduced when stpcpy() was added in Issue 7. Change back to the original text, i.e. change the NAME section to: stpcpy, strcpy - copy a string Bug 1779: Standard does not say how much read should do if a read-only variable is given Accepted as Marked https://austingroupbugs.net/view.php?id=1779 After bug 0001778 has been applied... Before P3291 L111882: If it is called in a subshell... Add a new sentence: Variables named before the one generating the error shall be set as described above; it is unspecified whether variables named later shall be set as above, or read simply ceases processing when the error occurs, leaving later named variables unaltered. Bug 1784: getopts specification needs fixing (multiple issues) OPEN https://austingroupbugs.net/view.php?id=1784 We started on this item and will continue next time. Next Steps -- We will continue on bug 1784 next time. The next call is on: Mon 2023-12-04 (Zoom meeting - general bugs/ballot resolution) Thu 2023-12-07 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Apologies in advance: Geoff Clare, 2023-12-04 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 27th November 2023 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew --- Minutes of the 27th November 2023 TeleconferenceAustin-1364 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 28th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Ahmet Acar Apologies Geoff Clare, The Open Group Tom Thompson, IEEE * General news Andrew noted that the action below to issue a status report is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1777: inaccuracy in find example 10 Accepted as Marked. https://austingroupbugs.net/view.php?id=1777 This item is tagged for TC3-2008 Change on P2924 line 97768 (find EXAMPLES): searches the file hierarchy for files of size 100 000 KiB or larger to: searches the file hierarchy for files of size larger than 100 000 KiB Change on P2924, L97770 (find EXAMPLES): find / -path /media -prune -o -size +19 -print to: find / −path /media −prune −o −size +20 −print Bug 1778: The read utility needs field splitting updates/corrections )and a little more) Accepted as Marked https://austingroupbugs.net/view.php?id=1778 On page 3291 line 111859 section read, change: By default, unless the -r option is specified, shall act as an escape character. An unescaped shall preserve the literal value of the following character, with the exception of ... to: If the -r option is not specified, shall act as an escape character. An unescaped shall preserve the literal value of a following and shall prevent a following byte (if any) from being used to split fields, with the exception of ... On page 3291 line 111869 section read, replace the paragraph beginning The terminating logical line delimiter and continuing down past the three bullet points to line 11878 (inclusive) with the following: The terminating logical line delimiter (if any) shall be removed from the input. Then if the shell variable IFS (see [xref XCU 2.5.3]) is set, and its value is an empty string, the resulting data shall be assigned to the variable named by the first var operand, and the variables named by other var operands (if any) shall be set to the empty string. No other processing shall be performed in this case. If IFS is unset, or is set to any non-empty value, then a modified version of the field splitting algorithm specified in [xref XCU 2.6.5] shall be applied, with the modifications as follows: The input to the algorithm shall be the logical line (minus terminating delimiter) that was read from standard input, and shall be considered as a single initial field, all of which resulted from expansions, with any escaped byte and the preceding escape character treated as if they were the result of a quoted expansion, and all other bytes treated as if they were the results of unquoted expansions. The loop over the contents of that initial field shall cease when either the input is empty or n output fields have been generated, where n is one less than the number of var operands passed to the read utility. Any remaining input in the original field being processed shall be returned to the read utility ``unsplit''; that is, unmodified except that any leading or trailing IFS white space, as defined in [xref to XCU 2.6.5], shall be removed. The specified var operands shall be processed in the order they appear on the command line, and the output fields generated by the field splitting algorithm shall be used in the order they were generated, by repeating the following checks until neither is true: If more than one var operand is yet to be processed and one or more output fields are yet to be used, the variable named by the first unprocessed var operand shall be assigned the value of the first unused output field. If exactly one var operand is yet to be processed and there was some remaining unsplit input returned from the modified field splitting algorithm, the variable named by the unprocessed var operand shall be assigned the unsplit input. If there are still one or more unprocessed var operands, each of the variables names by those operands shall be assigned an empty string. Note
Minutes of the 20th November 2023 Teleconference
hi All Enclosed are the minutes from today’s meeting regards Andrew - Minutes of the 20th November 2023 TeleconferenceAustin-1362 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Tom Thompson, IEEE Ahmet Acar * General news Andrew reported that the IEEE MEC has been resolved. We also finalized the last interpretation today. We are thus on target for issuing the next draft prior to the end of year break. Andrew noted that the action below to issue a status report is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. A reminder that there is no meeting on November 23rd (US Thanksgiving). * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1786: ed behavior on non-existing filename Accepted as Marked https://austingroupbugs.net/view.php?id=1786 We revised the change and recorded as bugnote 6577: On page 2797 line 92714 section ed ASYNCHRONOUS EVENTS, change: If the buffer is not empty and has changed since the last write, the to: If the buffer is not empty and the buffer change flag is currently set to either changed or changed-and-warned (see the EXTENDED DESCRIPTION section), the On page 2797 line 92725 section ed STDERR, change: The standard error shall be used only for diagnostic messages. to: The standard error shall be used for diagnostic messages and may be used for warning messages. On page 2797 line 92730 section ed EXTENDED DESCRIPTION, after: The ed utility shall operate on a copy of the file it is editing; changes made to the copy shall have no effect on the file until a w (write) command is given. The copy of the text is called the buffer. add these sentences: The ed utility shall keep track of whether the buffer has been modified. This shall be maintained as if via a tri-state internal flag with the state values unchanged, changed, and changed-and-warned, which is: Initially set to unchanged Set to changed by any command that modifies the buffer Set to unchanged by an e or E command that reloads (or empties) the buffer, or a w command that writes the entire buffer Set to either changed-and-warned or unchanged by an e or q command that warns an attempt was made to destroy the editor buffer A command that makes changes to the buffer in such a way that its contents are the same after the command (for example s/a/a/) shall be considered to have modified the buffer, unless explicitly stated otherwise. In the remainder of the description, this flag is referred to as the buffer change flag. On page 2800 line 92839 section ed EXTENDED DESCRIPTION, change: If changes have been made in the buffer since the last w command that wrote the entire buffer to: If the buffer change flag is currently set to changed On page 2800 line 92844, change: ... and shall continue in command mode with the current line number unchanged. If the e or q command is repeated with no intervening command, it shall take effect. to: ... and shall continue in command mode with the buffer change flag set to either changed-and-warned or unchanged and the current line number unchanged. If another e or q command is then attempted with no intervening command that sets the buffer change flag to changed, it shall take effect. On page 2801 line 92881, in the Append Command text, add a sentence: If is empty (that is, the terminating '.' immediately follows the 'a'), the buffer change flag shall not be altered. On page 2801 line 92901, in the Edit Command text, after the sentence: If no pathname is given, the currently remembered pathname, if any, shall be used (see the f command). insert another sentence: If the pathname names a file that does not exist and the buffer change flag is currently set to unchanged, it is unspecified whether this is treated as an error, or whether the resulting buffer is emptied and a warning is written to standard error instead of writing the byte count to standard out. On page 2801 line 92909, in the Edit Command text, change: If the buffer has changed since the last time the entire buffer was written to: If the buffer change flag is currently set to changed On page 2802 line 92914, in the Edit Without Checking Command text, change: shall
Minutes of the 16th November 2023 Teleconference
All Enclosed are the minutes from yesterday’s call regards Andrew Minutes of the 16th November 2023 TeleconferenceAustin-1362 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 17th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Apologies Tom Thompson, IEEE * General news On action items from last time: Eric raised an issue with the Etherpad and its use of non-open source javascript: AI:Andrew took an action to contact Richard Hansen to make him aware of the issue. Response:Andrew completed the action Don reminded us of the need to resolve the IEEE MEC comments on draft 3, to enable us to be able to submit draft 4 when we are ready. AI:Andrew and Geoff will meet on Thursday to finalize the response to IEEE and submit prior to the meeting. Response:Andrew and Geoff met and a final response to the D3 MEC comments was sent to the IEEE editor. After the meeting a reply was received from IEEE accepting our response, thus completing the requirement to address the MEC comments for the next draft. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. A reminder that there is no meeting on November 23rd (US Thanksgiving). We discussed the future meeting schedule and did not set a date yet after the November 20th meeting. We will discuss at that meeting. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1786: ed behavior on non-existing filename Reopened https://austingroupbugs.net/view.php?id=1786 This was reopened since we had received feedback from the GNU ed maintainer in bugnote 6570. A response was added in bugnote 6571 and the bug left open for further response. Based on Note: 0006570, we did some more investigation into existing implementations. It appears that most implementations clear the buffer change flag on an 'e' or 'q' that warned about a modified buffer, as in the following behavior: $ ed a text . q ? a . q $ where GNU ed was the outlier. The following modifications to the changes suggested at lines 92730 and 92845 in Note: 0006567 would capture that: On page 2797 line 92730 section ed EXTENDED DESCRIPTION, after: The ed utility shall operate on a copy of the file it is editing; changes made to the copy shall have no effect on the file until a w (write) command is given. The copy of the text is called the buffer. add these sentences: The ed utility shall keep track of whether the buffer has been modified. This shall be maintained as if via an internal flag which is set by any command that modifies the buffer and is cleared by a w command that writes the entire buffer, or by an e, E, or q command. A command that makes changes to the buffer in such a way that its contents are the same after the command (for example s/a/a/) shall be considered to have modified the buffer, unless explicitly stated otherwise. In the remainder of the description, this flag is referred to as the buffer change flag. On page 2800 line 92844, change: ... and shall continue in command mode with the current line number unchanged. If the e or q command is repeated with no intervening command, it shall take effect. to ... and shall continue in command mode with the buffer change flag cleared and the current line number unchanged. If another e or q command is then attempted with no intervening command that sets the buffer change flag, it shall take effect. We will continue on this item next time. Bug 1775: si_addr description confusingly over-specific Accepted https://austingroupbugs.net/view.php?id=1775 This item is tagged for TC3-2008. Bug 1776: find -newer any symlinks OPEN https://austingroupbugs.net/view.php?id=1776 We discussed this item and notes were made in the etherpad. We will pick up on this item next time. Next Steps -- The next call is on: Mon 2023-11-20 (Zoom meeting - general bugs/ballot resolution) There is no call on 2023-11-23 The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Apologies in advance: Geoff Clare, 2023-11-27 Andrew Josey, 2023-11-30 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
Minutes of the 13th November 2023 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew --- Minutes of the 13th November 2023 TeleconferenceAustin-1361 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 14th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Ahmet Acar Andrew Josey, The Open Group Apologies Tom Thompson, IEEE * General news Eric raised an issue with the Etherpad and its use of non-open source javascript: Administrivia: Antonio Diaz (maintainer of GNU ed) commented off-list that he was unable to review the Etherpad for on-going notes about potential changes to ed requirements, because the Etherpad depends on Javascript that does not include an open-source license (which he has disabled in his browser). Possible solutions: capture pdf renderings of the etherpad after the meeting for posting somewhere? AI:Andrew took an action to contact Richard Hansen to make him aware of the issue. Andrew confirmed that on 08 Nov 2023 the IEEE SA Standards Board approved the PAR extension request of P1003.1 Standard for Information Technology--Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 8 until 31 Dec 2024. A copy of the revised PAR (Project Authorization Request) has been added to the document register as document Austin/1360, see http://www.opengroup.org/austin/docreg.html. Andrew noted that due to a recent change in The Open Group systems now he also has to assign a role for users requesting GitLab access, so any new users will have to contact him to be setup. This does not impact existing users. Don reminded us of the need to resolve the IEEE MEC comments on draft 3, to enable us to be able to submit draft 4 when we are ready. Andrew and Geoff will meet on Thursday to finalize the response to IEEE and submit prior to the meeting. A reminder that there is no meeting on November 23rd (US Thanksgiving). * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1786: ed behavior on non-existing filename Accepted as Marked. https://austingroupbugs.net/view.php?id=1786 Eric took an action to point the GNU ed maintainer at the resolution, and if he finds any problems then we may reopen it. On page 2797 line 92714 section ed ASYNCHRONOUS EVENTS, change: If the buffer is not empty and has changed since the last write, the to: If the buffer is not empty and the buffer change flag is set (see the EXTENDED DESCRIPTION section), the On page 2797 line 92725 section ed STDERR, change: The standard error shall be used only for diagnostic messages. to: The standard error shall be used for diagnostic messages and may be used for warning messages. On page 2797 line 92730 section ed EXTENDED DESCRIPTION, after: The ed utility shall operate on a copy of the file it is editing; changes made to the copy shall have no effect on the file until a w (write) command is given. The copy of the text is called the buffer. add these sentences: The ed utility shall keep track of whether the buffer has been modified. This shall be maintained as if via an internal flag which is set by any command that modifies the buffer and is cleared by an e or E command that reloads (or empties) the buffer, or a w command that writes the entire buffer. A command that makes changes to the buffer in such a way that its contents are the same after the command (for example s/a/a/) shall be considered to have modified the buffer, unless explicitly stated otherwise. In the remainder of the description, this flag is referred to as the buffer change flag. On page 2800 line 92839 section ed EXTENDED DESCRIPTION, change: If changes have been made in the buffer since the last w command that wrote the entire buffer to: If the buffer change flag is set On page 2800 line 92845, change: If the e or q command is repeated with no intervening command, it shall take effect. to: If another e or q command is then attempted with no intervening command that sets the buffer change flag, it shall take effect. On page 2801 line 92881, in the Append Command text, add a sentence: If is empty (that is, the terminating '.' immediately follows the 'a'), the buffer change flag shall not be set. On page 2801 line 92901, in the Edit Command text, after the sentence: If no pathname is given, the currently remembered pathname, if any, shall be used (see the f command). insert another sentence: If the pathname names a file that does not exist and the buffer change flag is clear, it is unspecified whether this is treated as an error, or whether the resulting buffer is emptied
Approval of IEEE PAR Extension Request for P1003.1
For your information, I received the following notification today. We are pleased to inform you that on 08 Nov 2023 the IEEE SA Standards Board approved the PAR extension request of P1003.1 Standard for Information Technology--Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 8 until 31 Dec 2024. A copy of the revised PAR (Project Authorization Request) has been added to the document register as document Austin/1360, see http://www.opengroup.org/austin/docreg.html. regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 9th November 2023 Teleconference
All Enclosed are the minutes from yesterday’s meeting regards Andrew - Minutes of the 9th November 2023 TeleconferenceAustin-1359 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 10th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Andrew Josey, The Open Group Geoff Clare, The Open Group Tom Thompson, IEEE Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. * General news The IEEE PAR extension is still waiting on formal approval and expected soon. A reminder that there is no meeting on November 23rd (US Thanksgiving). * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1786: ed behavior on non-existing filename OPEN https://austingroupbugs.net/view.php?id=1786 We continued futher discussions on this item (details in the etherpad). We will continue on this item next time. Next Steps -- We will continue on bug 1786. The next call is on: Mon 2023-11-13 (Zoom meeting - general bugs/ballot resolution) Thu 2023-11-16 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 6th November 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew Minutes of the 6th November 2023 TeleconferenceAustin-1358 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 8th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Andrew Josey, The Open Group Apologies Eric Ackermann, HPI, University of Potsdam * General news The IEEE PAR extension is still waiting on formal approval and expected soon. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1786: ed behavior on non-existing filename OPEN https://austingroupbugs.net/view.php?id=1786 We continued discussion on this item (details in the etherpad). We will continue on this item next time. Next Steps -- We will continue on bug 1786. The next call is on: Thu 2023-11-09 (Zoom meeting - general bugs/ballot resolution) Mon 2023-11-13 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 2nd November 2023 Teleconference
All Enclosed are the minutes of the thursday meeting this week regards Andrew --- Minutes of the 2nd November 2023 TeleconferenceAustin-1357 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 4th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Andrew Josey, The Open Group Apologies Eric Ackermann, HPI, University of Potsdam Tom Thompson, IEEE * General news A reminder that the calls next week will revert to the usual offset in Europe, due to the US adjusting its clocks. As usual all calls are anchored on US time. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1780: The punctuation is confusing/ambiguous Accepted as marked https://www.austingroupbugs.net/view.php?id=1780 This item is tagged for TC3-2008 Change: The prioritization does add additional overhead to the message operations in those cases it is actually used but a clever implementation can optimize for the FIFO case to make that more efficient. to: The prioritization does add additional overhead to the message operations, in those cases it is actually used, but a clever implementation can optimize for the FIFO case to make that more efficient. Bug 1781: Factual error due to mis-wording with regard to timed wait functions? Accepted as Marked https://austingroupbugs.net/view.php?id=1781 This item is tagged for TC3-2008 Change: The pthread_cond_timedwait() function is given a relative timeout; the timeout may represent a deadline for an event. When these functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise. to: The pthread_cond_timedwait() function is given an absolute timeout; the timeout may represent a deadline for an event. When other functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise. Bug 1782: Standardize "pthread_yield"? Or change the example code? Accepted as Marked https://austingroupbugs.net/view.php?id=1782 This item is tagged for TC3-2008 Change: pthread_yield(); to: sched_yield(); The editor may also change the brace indentation to match other parts of the standard. (lines 123780-123794 and lines 123804-123847). Bug 1783: This sentence from this section is discussing thread safety isn't it? Accepted https://austingroupbugs.net/view.php?id=1783 This item is tagged for TC3-2008 Bug 1786: ed behavior on non-existing filename OPEN https://austingroupbugs.net/view.php?id=1786 We started discussion on this item (details in the etherpad). We will continue on this item next time. Next Steps -- We will continue on bug 1786. The next call is on: Mon 2023-11-06 (Zoom meeting - general bugs/ballot resolution) Thu 2023-11-09 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 30th October 2023 Teleconference
All
Enclosed are the minutes of the Monday meeting this week
regards
Andrew
---
Minutes of the 30th October 2023 TeleconferenceAustin-1356 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 1st November 2023
Attendees:
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Don Cragun, IEEE PASC OR
Geoff Clare, The Open Group
Mark Ziegast, SHware Systems Dev.
Eric Blake, Red Hat, The Open Group OR
Apologies
Andrew Josey, The Open Group
Eric Ackermann, HPI, University of Potsdam
Tom Thompson, IEEE
* General news
A reminder that the calls this week are one hour earlier in Europe
due to Europe adjusting its clocks.
* Current Business
Note for issue resolution all items are tagged for Issue 8 unless
noted otherwise or disposition is reject or duplicate.
Bug 251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Accepted as marked
https://austingroupbugs.net/view.php?id=251
We finished work on bug 251, except for some missing "" tags.
Don took an action to update the bug after the meeting.
See https://austingroupbugs.net/view.php?id=251#c6561 for the final changes.
Bug 248: Fix the numerous filename/pathname processing errors in specification
examples Accepted as Marked
https://austingroupbugs.net/view.php?id=248
Page and line numbers are for Issue 8 draft 3.
Page 2973, Line 99511 (hash APPLICATION USAGE):
Change:
find . −type f | xargs hash
To:
find . -type f -exec hash {} +
Page 3441, line 117538 (type APPLICATION USAGE):
Replace:
find . −type f | xargs type
with:
find . −type f -exec type {} +
On page 3568 line 18 (xargs EXAMPLES) change example 2 from:
The following command invokes diff with successive pairs of
arguments originally typed as command line arguments. It assumes
there are no embedded characters in the elements of
the original argument list.
printf "%s\n" "$@" | sed 's/[^[:alnum:]]/\\&/g' |
xargs -E "" -n 2 -x diff
to:
The following command invokes diff with successive pairs of
arguments originally typed as command line arguments.
printf "%s\0" "$@" | xargs -0 -n 2 -x diff --
On page 3568 line 122233 change example 3 from:
In the following commands, the user is asked which files in the
current directory (excluding dotfiles) are to be archived. The
files are archived into arch; a, one at a time or b, many at a
time. The commands assume that no filenames contain ,
, , , or double-quote characters.
a. ls | xargs -E "" -p -L 1 ar -r arch
b. ls | xargs -E "" -p -L 1 | xargs -E "" ar -r arch
to:
In the following command, the user is asked which regular files
below the current directory are to be archived.
find . -type f -print0 | xargs -0 -p -L 1 ar -r arch
On page 3568, lines 122242-122247 remove example 5
AI to EricB: Create new bug linked to bugid:1063 that changes hash
line 99517 to drop "" on PATH=$PATH example, and fixes text in
STDOUT line 99491 to state the list is cleared on assignment (not
merely on change). Possibly also move the details of the list of
remembered names up to DESCRIPTION instead of STDOUT. Also, sh
ENVIRONMENT VARIABLES line 113657 should probably mention hash table
effects; and add an xref to hash in 2.9.1.4 line 80882.
Next Steps
--
The next call is on:
Thu 2023-11-02 (Zoom meeting - general bugs/ballot resolution)
Mon 2023-11-06 (Zoom meeting - general bugs/ballot resolution)
The calls are for 90 minutes
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)
Andrew JoseyThe Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Re: Minutes of the 26th October 2023 Teleconference
hi all A correction to the minutes. It is the clocks in Europe that change this weekend! The calls will still be one hour earlier in Europe. The week after the US clocks will also change and we will be back in sync. Our calls are anchored on US time. regards Andrew > On 27 Oct 2023, at 12:39, Andrew Josey via austin-group-l at The Open Group > wrote: > > All > Enclosed are the minutes of yesterday’s call > > A reminder of the clocks change in the US this weekend, so the calls next > week are > 1 hour earlier in Europe. > > regards > Andrew > --- > > Minutes of the 26th October 2023 TeleconferenceAustin-1355 Page 1 of 1 > Submitted by Andrew Josey, The Open Group. 27th October 2023 > > Attendees: > Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR > Don Cragun, IEEE PASC OR > Andrew Josey, The Open Group > Geoff Clare, The Open Group > Tom Thompson, IEEE > Mark Ziegast, SHware Systems Dev. > Eric Blake, Red Hat, The Open Group OR > > Apologies > Eric Ackermann, HPI, University of Potsdam > > * General news > > Tom reported that the PAR extension is recommended for approval, > and should be ratified soon. > > We noted that the calls next week are one hour earlier in Europe > due to the US adjusting its clocks. Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 26th October 2023 Teleconference
All Enclosed are the minutes of yesterday’s call A reminder of the clocks change in the US this weekend, so the calls next week are 1 hour earlier in Europe. regards Andrew --- Minutes of the 26th October 2023 TeleconferenceAustin-1355 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 27th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies Eric Ackermann, HPI, University of Potsdam * General news Tom reported that the PAR extension is recommended for approval, and should be ratified soon. We noted that the calls next week are one hour earlier in Europe due to the US adjusting its clocks. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN https://austingroupbugs.net/view.php?id=251 We continued further discussion on this item. The changes are in https://posix.rhansen.org/p/bug251 We will continue next time. Next Steps -- We will continue on 251 The next call is on: Mon 2023-10-30 (Zoom meeting - general bugs/ballot resolution) Thu 2023-11-02 (Zoom meeting - general bugs/ballot resolution) Apologies in advance 2023-10-30 Andrew Josey The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 23rd October 2023 Teleconference
All Enclosed are the minutes for the Monday meeting this week regards Andrew __ Minutes of the 23rd October 2023 TeleconferenceAustin-1354 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 24th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies Eric Ackermann, HPI, University of Potsdam * General news We briefly discussed the proposed response to the outstanding MEC comments (relating to use of trademarks in text). We will respond to the IEEE editor in the week after November 5th. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN https://austingroupbugs.net/view.php?id=251 We continued discussion on this item. The changes are in https://posix.rhansen.org/p/bug251 We will continue next time. Next Steps -- We will continue on 251 The next call is on: Thu 2023-10-26 (Zoom meeting - general bugs/ballot resolution) Mon 2023-10-30 (Zoom meeting - general bugs/ballot resolution) Apologies in advance 2023-10-30 Andrew Josey The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 19th October 2023 Teleconference
All Enclosed are the minutes of yesterday’s call regards Andrew - Minutes of the 19th October 2023 TeleconferenceAustin-1352 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. Ahmet Acar Apologies Tom Thompson, IEEE Eric Ackermann, HPI, University of Potsdam * General news We discussed the proposed response to the outstanding MEC comments (relating to use of trademarks in text). In particular there was some discussion about whether we should remove the example of blockmode terminals. We will continue that item next time. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 700: Clarify strtoul's behaviour on strings representing negative numbers https://www.austingroupbugs.net/view.php?id=700 An issue was raised about bug 700, about whether an additional note was needed. however no change was made. The change to strtol() was a direct update based on a change in C99. The consensus was that no note is needed. Bug 251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN https://austingroupbugs.net/view.php?id=251 We continued discussion on this item. We decided that we should not reject the bug (given https://austingroupbugs.net/view.php?id=251#c6484) The changes are in https://posix.rhansen.org/p/bug251 We will continue next time. Next Steps -- We will continue on 251 The next call is on: Mon 2023-10-23 (Zoom meeting - general bugs/ballot resolution) Thu 2023-10-26 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 16th October 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew Minutes of the 16th October 2023 TeleconferenceAustin-1351 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 14th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. Apologies Tom Thompson, IEEE * General news Andrew took an action to develop a response to the outstanding MEC comments (relating to use of trademarks in text, for example saying we met at the IBM facility!). * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Accepted as Marked https://austingroupbugs.net/view.php?id=657 This item is tagged for Issue 8. An interpretation is required. Interpretation response: The standard is unclear on this issue, and 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): Page and line numbers are for Issue 8 draft 3. Change "size" (when talking about the argument) to "max_size" throughout. Change "size" (when talking about the last position in the buffer) to "end position" throughout. Change on P961, L32741: Open the stream for update (reading and writing). Truncate the buffer contents. to: Open the stream for update (reading and writing). Change P961, L32744-32745 from: If the mode argument includes 'b', then the stream shall be in binary mode; otherwise the stream shall be in text mode. to: If the mode argument begins with 'w' and max_size is not zero, the buffer contents shall be truncated by writing a null byte at the beginning. If the mode argument includes 'b', the results are implementation-defined. Change on P961, L32758-32762: The stream shall also maintain the size of the current buffer contents; use of fseek() or fseeko() on the stream with SEEK_END shall seek relative to this size. If mode starts with 'r' or includes 'b', the size shall be set to the value given by the size argument and shall not change. Otherwise, the stream is in text mode and writable, and the size shall be variable; for modes w and w+ the initial size shall be zero and for modes a and a+ the initial size shall be: to: The stream shall also maintain the end position of the current buffer contents; use of fseek() or fseeko() on the stream with SEEK_END shall seek relative to this end position. If mode starts with 'r' the end position shall be set to the value given by the max_size argument and shall not change. Otherwise, the stream is writable and the end position shall be variable; for modes w and w+ the initial end position shall be zero and for modes a and a+ the initial end position shall be: Change on P962, L32775-32776: When a stream open for writing in text mode is flushed or closed, a null byte shall be written at the current position or at the end of the buffer, depending on the size of the contents. If a stream open for update in text mode is flushed or closed and the last write has advanced the current buffer size, a null byte shall be written at the end of the buffer if it fits. If a stream is opened in binary mode, no additional null byte shall be written. to: When a stream open for update (the mode argument includes '+') or for writing only is successfully written and the write advances the current buffer end position, a null byte shall be written at the new buffer end position if it fits. Change on P963, L32822-32828: Unlike fopen(), where a 'b' in the mode argument is required to have no effect, fmemopen() distinguishes between text and binary modes. Text mode guarantees that the underlying memory will always be null terminated after any write operation, and tracks the growth of the largest position written to up to that point; while binary mode only modifies the underlying buffer according to direct writes, while seeking relative to the full buffer size. The combination of append and binary modes is not commonly used, since any attempt to write to such a stream will necessarily fail because the stream does not dynamically grow beyond the initial size. to: Implementations differ as regards how a 'b' in the mode argument affects the behavior. For some the 'b' has no effect, as is required for fopen(); others distinguish between text and binary mo
Interpretation for a 30 day review
hi All The following interpretation has been proposed and is commencing a 30 day review Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified https://www.austingroupbugs.net/view.php?id=657 Comments are due back by November 17 2023 regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 12th October 2023 Teleconference
All These are the minutes from the thursday meeting this week regards Andrew Minutes of the 12th October 2023 TeleconferenceAustin-1351 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 14th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Andrew Josey, The Open Group Geoff Clare, The Open Group Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. Apologies Eric Blake, Red Hat, The Open Group OR * General news We briefly discussed status of the draft, Geoff noted that all the bug reports have been implemented in the draft. He also noted we need to clear the final MEC comments from the IEEE editors before moving forward. Andrew took an action to manage the MEC comments (relating to use of trademarks in text, for example saying we met at the IBM facility!). * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN https://austingroupbugs.net/view.php?id=657 We continued the discussion of this item, with notes in the etherpad. We discussed whether to issue an interpretation, which would impact the next draft date. We will continue this next time. Next Steps -- After bug 657, we will pick up on 251 (Don's proposal is ready) The next call is on: Mon 2023-10-16 (Zoom meeting - general bugs/ballot resolution) Thu 2023-10-19 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 9th October 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew --- Minutes of the 9th October 2023 TeleconferenceAustin-1350 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Andrew Josey, The Open Group Geoff Clare, The Open Group Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. Apologies Eric Blake, Red Hat, The Open Group OR * General news We briefly discussed status of the PASC dissolution and the P1003.1 committee moving under the Microprocessor Committee, but there is no news yet. We also confirmed that the date for the PAR extension to be considered for extension is the October 25th. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN https://austingroupbugs.net/view.php?id=657 We continued the discussion of this item, with notes in the etherpad. We will continue this next time. Next Steps -- After bug 657, we will pick up on 251 (if Don's proposal is ready) The next call is on: Thu 2023-10-12 (Zoom meeting - general bugs/ballot resolution) Mon 2023-10-16 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Eric Blake 2023-10-12 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Re: Minutes of the 5th October 2023 Teleconference
hi All Please note the following correction to the minutes for bug 1771 > On 6 Oct 2023, at 19:54, Andrew Josey via austin-group-l at The Open Group > wrote: > > > Bug 1771 > https://austingroupbugs.net/view.php?id=1771 Accepted as Marked > > This bug was updated. Part of the resolution is changed as marked below. > > A note was added after we updated the resolution, pointing out that > ksh93 already uses printf %Q for something else. > > 2nd para: > >A future version of this standard may add a %q or %Q conversion >(or both) to convert a string argument to a quoted output format >that can be reused as shell input. Note 0006470 has been updated to change: A future version of this standard may add a %q or %Q conversion (or both) to convert a string argument to a quoted output format that can be reused as shell input. to: A future version of this standard may add a %q conversion to convert a string argument to a quoted output format that can be reused as shell input. regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 5th October 2023 Teleconference
All Enclosed are the minutes of the thursday meeting this week regards Andrew == Minutes of the 5th October 2023 TeleconferenceAustin-1349 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 6th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Andrew Josey, The Open Group Geoff Clare, The Open Group Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. * General news Reminder: We agreed to meet on October 9, even though that is a US holiday. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1771 https://austingroupbugs.net/view.php?id=1771 Accepted as Marked This bug was updated. Part of the resolution is changed as marked below. A note was added after we updated the resolution, pointing out that ksh93 already uses printf %Q for something else. 2nd para: A future version of this standard may add a %q or %Q conversion (or both) to convert a string argument to a quoted output format that can be reused as shell input. Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN https://austingroupbugs.net/view.php?id=657 We discussed this at length, with notes in the etherpad. We will continue this next time. Next Steps -- After bug 657, we will pick up on 251 (if Don's proposal is ready) The next call is on: Mon 2023-10-09 (Zoom meeting - general bugs/ballot resolution) Thu 2023-10-12 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Eric Blake 2023-10-09, 2023-10-12 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 2nd October 2023 Teleconference
hi all Enclosed are the minutes of the Monday meeting this week regards Andrew --- Minutes of the 2nd October 2023 TeleconferenceAustin-1348 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 4th October 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Andrew Josey, The Open Group Geoff Clare, The Open Group Ahmet Acar Mark Ziegast, SHware Systems Dev. Apologies Tom Thompson, IEEE * General news We agreed to meet on October 9, even though that is a US holiday. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong https://austingroupbugs.net/view.php?id=1649 Accepted as Marked The comments in Note: 0006495, Note: 0006496, Note: 0006497, Note: 0006498, and Note: 0006499 were discussed during the 2023-10-02 conference call. All of the changes suggested in Note: 0006495 were accepted. We also accepted the suggested change from "data bytes" to "bytes". All of these changes have be updated in Note: 0006488. This bug remains resolved with the changes now specified in Note: 0006488. See https://austingroupbugs.net/view.php?id=1649#c6488 Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN https://austingroupbugs.net/view.php?id=657 We discussed this at length, with notes in the etherpad. We will continue this next time. Next Steps -- After bug 657, we will pick up on 251 (if Don's proposal is ready) The next call is on: Thu 2023-10-05 (Zoom meeting - general bugs/ballot resolution) Mon 2023-10-09 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Eric Blake 2023-10-09, 2023-10-12 The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 28th September 2023 Teleconference
All Enclosed are the minutes of the thursday meeting this week regards Andrew Minutes of the 28th September 2023 TeleconferenceAustin-1347 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 29th September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Tom Thompson, IEEE Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Ahmet Acar Apologies Geoff Clare, The Open Group * General news Tom reported that there is no further update yet on the change of sponsor for the IEEE POSIX work, but he will keep us informed. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong https://austingroupbugs.net/view.php?id=1649 Accepted as Marked We had received a comment from KRE about whitespace layout. Don took an action to update the final bugnote accordingly. See https://austingroupbugs.net/view.php?id=1649#c6488 Bug 657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN https://austingroupbugs.net/view.php?id=657 We discussed this at length, with notes in the etherpad. We will continue this next time. Next Steps -- After bug 657, we will pick up on 251 (if Don's proposal is ready) The next call is on: Mon 2023-10-02 (Zoom meeting - general bugs/ballot resolution) Thu 2023-10-05 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Geoff Clare maybe 2023-10-02 Eric Blake 2023-10-09, 2023-10-12 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 25th September 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew - Minutes of the 25th September 2023 TeleconferenceAustin-1346 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 27 September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Tom Thompson, IEEE Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Apologies Geoff Clare, The Open Group * General news Tom reported that the PASC policies and procedures had been approved, also the PAR extension request is on the agenda for the next IEEE approval meeting in October. He also reported that the dissolution of the PASC had been approved and that the project would be moving soon under the Microprocessor Committee as the new sponsor. We asked Tom to keep us informed of the move. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong https://austingroupbugs.net/view.php?id=1649 Accepted as Marked This item was reopened and revisions made. Replace XCU section 2.6.5 on issue 8 draft 3 P2476, L80478-80504 with: After parameter expansion (Section 2.6.2), command substitution (Section 2.6.3), and arithmetic expansion (Section 2.6.4), and if the shell variable IFS [xref XCU 2.5.3] is set and its value is not empty, or if the IFS variable is unset, the shell shall scan each field containing results of expansions and substitutions that did not occur in double-quotes for field splitting; zero, one or multiple fields can result. For the remainder of this section, any reference to the results of an expansion, or results of expansions, shall be interpreted to mean the results from one or more unquoted variable or arithmetic expansions, or unquoted command substitutions. If the IFS variable is set and has an empty string as its value, no field splitting occurs. However if an input field which contained the results of an expansion is entirely empty, it shall be removed. Note that this occurs before quote removal, any input field that contains any quoting characters can never be empty at this point. After the removal of any such fields from the input, the possibly modified input field list becomes the output. Each input field is considered in sequence, first to last, with the results of the algorithm described in this section causing output fields to be generated, which remain in the same order as the input fields from which they originated. Fields which contain no results from expansions shall not be affected by field splitting, and shall remain unaltered, simply moving from the list of input fields to be next in the list of output fields. In the remainder of this description, it is assumed that there is present in the field at least one expansion result, this assumption will not be restated. Field splitting only ever alters those parts of the field. For the purposes of this section, the term "IFS white space" shall mean any of the white-space bytes [xref to XBD 3.412, 3.413, and 3.414] , or from the Portable Character Set [xref XBD 6.1] which are present in the value of the IFS variable, and perhaps other white-space characters. It is implementation defined whether other white-space characters which appear in the value of IFS are also considered as "IFS white space". The three characters above specified as IFS white-space bytes are always IFS white space, when they occur in the value of IFS, regardless of whether they are white-space characters in any relevant locale. For other locale specific white-space characters allowed by the implementation it is unspecified whether the character is considered as IFS white space if it is white space at the time it is assigned to the IFS variable, or if it is white space at the time field splitting occurs (the locale may have changed between those events). If the IFS variable is unset, then for the purposes of this section, but without altering the value of the variable, its value shall be considered to contain the three single byte characters , and from the portable character set, all of which are IFS white-space characters. The shell shall use the byte sequences that form the characters in the value of the IFS variable as delimiters. Each of the characters and which appears in the value of IFS shall be a single byte delimiter. The shell shall use these delimiters as field terminators to split the results of expansions, along with other adjacent bytes, into separate fields
Minutes of the 21st September 2023 Teleconference
All Enclosed are the minutes from yesterday’s call regards Andrew -- Minutes of the 21st September 2023 TeleconferenceAustin-1345 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 22 September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. Apologies Geoff Clare, The Open Group Tom Thompson, IEEE Andrew Josey, The Open Group * General news None. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong https://austingroupbugs.net/view.php?id=1649 Accepted as Marked Replace XCU section 2.6.5 on issue 8 draft 3 P2476, L80478-80504 with: After parameter expansion (Section 2.6.2), command substitution (Section 2.6.3), and arithmetic expansion (Section 2.6.4), and if the shell variable IFS [xref XCU 2.5.3] is set and its value is not empty, or if the IFS variable is unset, the shell shall scan each field containing results of expansions and substitutions that did not occur in double-quotes for field splitting; zero, one or multiple fields can result. For the remainder of this section, any reference to the results of an expansion, or results of expansions, shall be interpreted to mean the results from one or more unquoted variable or arithmetic expansions, or unquoted command substitutions. If the IFS variable is set and has an empty string as its value, no field splitting occurs. However if an input field which contained the results of an expansion is entirely empty, it shall be removed. Note that this occurs before quote removal, any input field that contains any quoting characters can never be empty at this point. After the removal of any such fields from the input, the possibly modified input field list becomes the output. Each input field is considered in sequence, first to last, with the results of the algorithm described in this section causing output fields to be generated, which remain in the same order as the input fields from which they originated. Fields which contain no results from expansions shall not be affected by field splitting, and shall remain unaltered, simply moving from the list of input fields to be next in the list of output fields. In the remainder of this description, it is assumed that there is present in the field at least one expansion result, this assumption will not be restated. Field splitting only ever alters those parts of the field. For the purposes of this section, the term "IFS white space" shall mean any of the single byte characters , or from the Portable Character Set [xref XBD 6.1] which are present in the value of the IFS variable, and perhaps other White Space characters. It is implementation defined whether other White Space characters which appear in the value of IFS are also considered as "IFS white space". The three characters above specified as IFS white space characters are always IFS white space, when they occur in the value of IFS, regardless of whether they are White Space characters in any relevant locale. For other locale specific White Space characters allowed by the implementation it is unspecified whether the character is considered as IFS white space if it is White Space at the time it is assigned to the IFS variable, or if it is White Space at the time field splitting occurs (the locale may have altered between those events). If the IFS variable is unset, then for the purposes of this section, but without altering the value of the variable, its value shall be considered to contain the three single byte characters , and from the Portable Character Set, all of which are IFS white space characters. The shell shall use the byte sequences that form the characters in the value of the IFS variable as delimiters. Each of the characters and which appears in the value of IFS shall be a single byte delimiter. The shell shall use these delimiters as field terminators to split the results of expansions, along with other adjacent bytes, into separate fields, as described below. Note that these delimiters terminate a field, they do not, of themselves, cause a new field to start, subsequent data bytes that are not from the results of an expansion, or that do not form IFS white space characters are required for a new field to begin. Note that the shell processes arbitrary bytes from the input fields, there is no requirement that those bytes form valid characters. If resu
Minutes of the 18th September 2023 Teleconference
All Enclosed are the minutes of today’s meeting regards Andrew - Minutes of the 18th September 2023 TeleconferenceAustin-1344 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 18 September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. Ahmet Acar, (student) Apologies Geoff Clare, The Open Group Tom Thompson, IEEE * General news Andrew reported that the approval from PASC SEC for extending the PAR has been received and the matter will be at the next IEEE approvals meeting in October. Andrew reported that Joe Gwinn had reported on the dissolution of the PASC commitee at the recent IEEE CS/SAB meeting. This will impact where the 1003.1 committee reports into. Don will take brief notes on Thursday and send to Andrew for production of the minutes. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong https://austingroupbugs.net/view.php?id=1649 OPEN We discussed this item (again) at length (notes in the etherpad). Next Steps -- We will pick up on bug 1649 next time, and then 251 (if Don's proposal is ready) The next call is on: Thu 2023-09-21 (Zoom meeting - general bugs/ballot resolution) Mon 2023-09-25 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Geoff Clare 2023-09-11 through 2023-09-28, maybe 2023-10-02 Andrew Josey 2023-09-21 The calls are for 90 minutes 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) Andrew Josey, The Open Group, ajo...@opengroup.org
Minutes of the 11th September 2023 Teleconference
All Enclosed are the minutes of today’s meeting regards Andrew - Minutes of the 11th September 2023 TeleconferenceAustin-1343 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11th September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies Geoff Clare, The Open Group Tom Thompson, IEEE * General news There will be no meeting on September 14th. We discussed the IEEE PAR extension. Andrew has called for approval by the PASC SEC. He will proceed with the submission and then it will be down to Joe Gwinn to approve it going forward. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong https://austingroupbugs.net/view.php?id=1649 OPEN We discussed this item at length (notes in the etherpad). Next Steps -- We will pick up on bug 1649 next time, and then 251 (if Don's proposal is ready) The next call is on: Thu 2023-09-14 NO MEETING Mon 2023-09-18 (Zoom meeting - general bugs/ballot resolution) Thu 2023-09-21 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Geoff Clare 2023-09-11 through 2023-09-28, maybe 2023-10-02 Andrew Josey 2023-09-21 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 7th September 2023 Teleconference
All Enclosed are the minutes of yesterday’s call regards Andrew --- Minutes of the 7th September 2023 TeleconferenceAustin-1342 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 8th September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Tom Thompson * General news There will be no meeting on September 14th. We discussed the PAR extension and Tom took an action to send Andrew instructions. Andrew took an action to email the PASC SEC for approval for the extension. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1771: support or reserve %q as printf-utility format specifier Accepted as Marked https://austingroupbugs.net/view.php?id=1771 We agreed to revisit this item and updated the response: After page 3275 line 111227 section printf, add two paragraphs to FUTURE DIRECTIONS: A future version of this standard is expected to add a %b conversion to the printf() function for binary conversion of integers, in alignment with the next version of the ISO C standard. This will result in an inconsistency between the printf utility and printf() function for format strings containing %b. Implementors are encouraged to collaborate on a way to address this which could then be adopted in a future version of this standard. For example, the printf utility could add a -C option to make the format string behave in the same way, as far as possible, as the printf() function. A future version of this standard may add a %q or %Q conversion (or both) to convert a string argument to a quoted output format that can be reused as shell input. Next Steps -- We will pick up on bug 251 next time (if Don's proposal is ready) The next call is on: Mon 2023-09-11 (Zoom meeting - general bugs/ballot resolution) Thu 2023-09-14 NO MEETING Mon 2023-09-18 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Geoff Clare 2023-09-11 through 2023-09-28, maybe 2023-10-02 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 31st August 2023 Teleconference
All Enclosed are the minutes of the thursday call this week regards Andrew - Minutes of the 31st August 2023 TeleconferenceAustin-1341 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 1st September 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Apologies Tom Thompson * General news A reminder that there is no meeting on 2023-09-04 as this is a US holiday. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1771: support or reserve %q as printf-utility format specifier Accepted as Marked https://austingroupbugs.net/view.php?id=1771 Note: https://debbugs.gnu.org/65659 has been opened against GNU Coreutils to get their feedback. On page 2793 line 92597-92599 section echo, add a sentence after the example: However, this usage of %b with the printf utility is now obsolescent, and applications desiring escape sequence processing on non-XSI implementations should instead place escape sequences (other than \c) to be processed in the format string of the printf utility. On page 3269 line 111000-111019 section printf, add OB shading to list item 7 (b conversion) On page 3271 line 04 section printf, change: The %b conversion specification is not part of the ISO C standard; it has been added here as a portable way to process -escapes expanded in string operands as provided by the echo utility. See also the APPLICATION USAGE section of [xref to echo] for ways to use printf as a replacement for all of the traditional versions of the echo utility. to: The %b conversion was originally added as a portable way to process -escapes expanded in string operands as provided by the echo utility on XSI implementations. However, it will conflict with the next version of the ISO C standard, which is adding it for binary output of integers, and has consequently been marked obsolescent. After page 3275 line 111227 section printf, add two paragraphs to FUTURE DIRECTIONS: A future version of this standard may change the %b conversion to a binary conversion in alignment with the next version of the ISO C standard. It is recommended that implementations treat the "%#s" conversion specification, which is undefined by this standard, as a synonym for the current "%b" behavior; this can then be added in a future version of this standard once there is existing practice. A future version of this standard may add a %q or %Q conversion (or both) to convert a string argument to a quoted output format that can be reused as shell input. Next Steps -- We will pick up on bug 251 next time (if Don's proposal is ready) The next call is on: Thu 2023-09-07 (Zoom meeting - general bugs/ballot resolution) Mon 2023-09-11 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Geoff Clare 2023-09-11 through 2023-09-28, maybe 2023-10-02 The calls are for 90 minutes 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) ---- Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 21st August 2023 Teleconference
All Enclosed are the minutes of today’s meeting regards Andrew - Minutes of the 21st August 2023 TeleconferenceAustin-1339 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 21st August 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, HPI, University of Potsdam Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies Tom Thompson * General news A reminder that there are no meetings on 2023-08-28, 2023-09-04 as these are UK and US holidays. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. +Bug 251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don reported he was working on the action to develop a proposed resolution. We will come back to the item when the action is completed. Bug 1772: make's ASYNCHRONOUS EVENTS has several problems Accepted as Marked https://austingroupbugs.net/view.php?id=1772 Make the following changes: On page 2339 line 74433 section 1.4, change: Default Behavior: When this section is listed as ``Default.'', or it refers to ``the standard action for all other signals; see Section 1.4 (on page 2336)'' it means ... to: Default Behavior: When this section is listed as ``Default.'', or it refers to ``the standard action'' for any signal, it means ... On page 2971 line 98562 section make, after applying bug 523 replace the text of the ASYNCHRONOUS EVENTS section with: For SIGHUP, SIGINT, SIGQUIT, and SIGTERM signals, if the signal was not inherited as ignored, none of the -n, -p, or -q options was specified, make is currently processing a target or inference rule, the current target is neither a directory nor a prerequisite of the special targets .PHONY or .PRECIOUS: make shall catch the signal and, if the time of last data modification of the current target has changed since make began processing the rule to bring that target up to date, remove that target; it may also remove that target if the time of last data modification has not changed. Any targets removed in this manner shall be reported in diagnostic or informational messages of unspecified format, written to standard error. If make writes a diagnostic message to standard error, it shall exit with a status that indicates an error occurred; otherwise, it shall set the signal to default and re-signal itself. In all other circumstances, make shall take the standard action for all signals; see [xref to 1.4]. On page 2972 line 98577 section make, change STDERR from: The standard error shall be used only for diagnostic messages. to: The standard error shall be used for diagnostic messages and may be used for informational messages about target removals (see ASYNCHRONOUS EVENTS). Next Steps -- If the action on 251 completes we will start on that next time. The next call is on: Thu 2023-08-24 (Zoom meeting - general bugs/ballot resolution) Mon 2023-08-31 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Tom Thompson 2023-08-14 through 2023-08-28 Andrew Josey, 2023-08-24 Geoff Clare 2023-09-11 through 2023-09-28, maybe 2023-10-02 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 17th August 2023 Teleconference
All Enclosed are the minutes of yesterday’s call regards Andrew -- Minutes of the 17th August 2023 TeleconferenceAustin-1338 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 18th August 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, HPI, University of Potsdam Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies Tom Thompson * General news We agreed that no meetings will be held on 2023-08-28, 2023-09-04 as these are UK and US holidays. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. +Bug 251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 The call discussed this item and will continue next time. Next Steps -- The next call is on: Mon 2023-08-21 (Zoom meeting - general bugs/ballot resolution) Thu 2023-08-24 (Zoom meeting - general bugs/ballot resolution) Apologies in advance: Tom Thompson 2023-08-14 through 2023-08-28 Andrew Josey, 2023-08-24, 2023-08-28 Geoff Clare 2023-09-11 through 2023-09-28, maybe 2023-10-02 The calls are for 90 minutes 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 14th August 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew Minutes of the 14th August 2023 TeleconferenceAustin-1337 Page 1 of 1 Submitted by Geoff Clare, The Open Group. 16th August 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, HPI, University of Potsdam Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Mark Ziegast, SHware Systems Dev. (late) Andrew Josey, The Open Group (partial) Apologies Tom Thompson * General news None * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1627: XSH 3 / mktime() is woefully underspecified Accepted as Marked https://austingroupbugs.net/view.php?id=1627 On page 113 line 3186 section 4.16 Seconds Since the Epoch, change: The relationship between the actual time of day and the current value for seconds since the Epoch is unspecified. to: The relationship between the actual date and time in Coordinated Universal Time, as determined by the International Earth Rotation Service, and the system's current value for seconds since the Epoch is unspecified. On page 1331 line 44320 section mktime(), after applying bugs 1613 and 1614 change: The relationship between the tm structure (defined in the header) and the time in seconds since the Epoch is that the result shall be as specified in the expression given in the definition of seconds since the Epoch (see [xref to XBD 4.19]) corrected for the offset of the timezone's standard time from Coordinated Universal Time and further corrected (if applicable--see below) for Daylight Saving Time, where the names other than tm_yday in the structure and in the expression correspond, and the tm_yday value used in the expression is the day of the year from 0 to 365 inclusive, calculated from the members of the tm structure specified above. to: The mktime() function shall calculate the time in seconds since the Epoch to be returned as if by manipulating the members of the tm structure according to the following steps. 1. The tm_sec member may, but should not, be brought into the range 0 to 60, inclusive. For each 60 seconds added to or subtracted from tm_sec, a decrement or increment, respectively, of 1 minute shall be saved for later application. 2. The tm_min member shall be brought into the range 0 to 59, inclusive, and any saved decrement or increment of minutes shall then be applied, repeating the range adjustment afterwards if necessary. For each 60 minutes added to or subtracted from tm_min, a decrement or increment, respectively, of 1 hour shall be saved for later application. 3. The tm_hour member shall be brought into the range 0 to 23, inclusive, and any saved decrement or increment of hours shall then be applied, repeating the range adjustment afterwards if necessary. For each 24 hours added to or subtracted from tm_hour, a decrement or increment, respectively, of 1 day shall be saved for later application. 4. The tm_mon member shall be brought into the range 0 to 11, inclusive. For each 12 months added to or subtracted from tm_mon, a decrement or increment, respectively, of 1 year shall be saved for later use. 5. The tm_mday member shall be brought into the range 1 to 31, inclusive, and any saved decrement or increment of days shall then be applied, repeating the range adjustment afterwards if necessary. Adjustments downwards shall be applied by subtracting the number of days (according to the Gregorian calendar) in month tm_mon+1 of the year obtained by adding/subtracting any saved increment/decrement of years to the value tm_year+1900, and then incrementing tm_mon by 1, repeated as necessary. Adjustments upwards shall be applied by adding the number of days in the month before month tm_mon+1 of the year obtained by adding/subtracting any saved increment/decrement of years to the value tm_year+1900, and then decrementing tm_mon by 1, repeated as necessary. During these adjustments, the tm_mon value shall be kept within the range 0 to 11, inclusive, by applying step 4 as necessary. 6. If the tm_mday member is greater than the number of days in month tm_mon+1 of the year obtained by adding/subtracting any saved increment/decrement of years to the value tm_year+1900, that number of days shall be subtracted from tm_mday, and tm_mon shall be incremented by 1. If this results in tm_mon having the value 12, step 4 shall be applied. 7. The number of seconds since the Epoch in Coordinated Universal Time shall be calculated from the range-corrected values of the relevant tm structure members (or the original value where a member
Interpretations for a 30 day review
hi All The following interpretations have been proposed and are now commencing a 30 day review Bug 689: Possibly unintended allowance for stdio deadlock https://www.austingroupbugs.net/view.php?id=689 Bug 1273: glob()'s GLOB_ERR/errfunc and non-directory files https://austingroupbugs.net/view.php?id=1273 Any comments are due back by September 14 2023 regards Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 3rd August 2023 Teleconference
All Enclosed are the minutes of today’s meeting regards Andrew --- Minutes of the 3rd August 2023 TeleconferenceAustin-1334 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 3rd August 2023 Attendees: Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Tom Thompson, IEEE Andrew Josey, The Open Group (joined late) Mark Ziegast, SHware Systems Dev. (joined late) Apologies Eric Ackermann, HPI, University of Potsdam * General news We discussed draft planning, and tentatively agreed we will submit a request to extend the PAR so as to cover the case of us not making the cutoff date for the IEEE December approvals (October 16). Andrew will investigate this further in the week commencing August 14. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1273: glob()'s GLOB_ERR/errfunc and non-directory files OPEN https://austingroupbugs.net/view.php?id=1273 The meeting spent much time discussing this issue and will continue on it next time. The next item up after that is Bug 1406: clarification of SEEK_END when current pointer doesn't match buffer size https://austingroupbugs.net/view.php?id=1406 Next Steps -- The next call is on: Mon 2023-08-07 (Zoom meeting - general bugs/ballot resolution) Thu 2023-08-10 (Zoom meeting - general bugs/ballot resolution) Mon 2023-08-14 (Zoom meeting - general bugs/ballot resolution) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Apologies in advance: Andrew Josey 2023-08-07, 2023-08-10 Tom Thompson 2023-08-14 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 31st July 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew - Minutes of the 31st July 2023 TeleconferenceAustin-1333 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd August 2023 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Apologies Tom Thompson, IEEE Eric Ackermann, HPI, University of Potsdam * General news The meeting on August 3rd will be a zoom meeting. Andrew noted that draft planning is still to be done. It is noted that the cutoff for the IEEE December approvals is October 16. We will likely need two more drafts from here. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1732: cp and mv EXIT STATUS does not account for -i Accepted as Marked https://austingroupbugs.net/view.php?id=1732 This item is tagged for TC3-2008. An interpretation is required. Interpretation response: The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The cp and mv utility's EXIT STATUS sections did not properly account for the interaction with the -i option. Notes to the Editor (not part of this interpretation): On page 2609 line 84793 section cp, change: All input files were copied successfully. to: All requested files (excluding files where a non-affirmative response was given to a request for confirmation) were successfully copied. On page 3020 line 100451 section mv, change: All input files were moved successfully. to: All requested files (excluding files where a non-affirmative response was given to a request for confirmation) were successfully moved. On page 3200, line 107342-107343 section rm, change: Each directory entry was successfully removed, unless its removal was canceled by a non-affirmative response to a prompt for confirmation. to: All requested directory entries (excluding directory entries where a non-affirmative response was given to a request for confirmation) were successfully deleted. Bug 1731: pthread_sigmask() pending signal requirement time paradox Accepted as Marked https://austingroupbugs.net/view.php?id=1731 This item is tagged for TC3-2008. After applying bug 1636, change: If there are any pending unblocked signals after the call to pthread_sigmask(), at least one of those signals shall be delivered before the call to pthread_sigmask() returns. to: If the argument set is not a null pointer, after pthread_sigmask() changes the currently blocked set of signals it shall determine whether there are any pending unblocked signals; if there are any, then at least one of those signals shall be delivered before the call to pthread_sigmask() returns. On page 1736 line 56316 section pthread_sigmask(), change APPLICATION USAGE from: None. to: Although pthread_sigmask() has to deliver at least one of any pending unblocked signals that exist after it has changed the currently blocked set of signals, there is no requirement that the delivered signal(s) include any that were unblocked by the change. If one or more signals that were already unblocked become pending (see [xref to 2.4.1]) during the period the pthread_setmask() call is executing, the signal(s) delivered before the call returns might include only those signals. Bug 1730: m4 synopsis does not show file operand as optional Accepted https://austingroupbugs.net/view.php?id=1730 This item is tagged for TC3-2008. Bug 1729: mkdir() ENOENT and ENOTDIR overlap Accepted https://austingroupbugs.net/view.php?id=1729 This item is tagged for TC3-2008. Bug 1728: typo on the getprotobyname() pointer page Accepted https://austingroupbugs.net/view.php?id=1728 This item is tagged for TC3-2008. Bug 1725: mailx: *screen*: specify default Accepted https://austingroupbugs.net/view.php?id=1725 This item is tagged for TC3-2008. Bug 1674: may posix_spawnp() fail with ENOEXEC? Accepted as Marked https://austingroupbugs.net/view.php?id=1674 Accepted as marked, interpretation required, issue8 tag. An interpretation is required. Interpretation response: 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 changes in the Desired Action, and also the changes in Note: 0006264. Bug 1649: Field splitting is woefully under specified, and in places, simply wrong OPEN https://austingroupbugs.net/view.php?id=1649 We will wait
Interpretations for a 30 day review
hi All The following interpretations have been proposed and are now commencing a 30 day review Bug 0001732: cp and mv EXIT STATUS does not account for -i https://austingroupbugs.net/view.php?id=1732 Bug 0001674: may posix_spawnp() fail with ENOEXEC? https://austingroupbugs.net/view.php?id=1674 Any comments are due back by August 31 2023 regards Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Interpretations for a 30 day review
hi All The following interpretations have been proposed and are now commencing a 30 day review Bug 1614: XSH 3/mktime does not specify EINVAL and should https://austingroupbugs.net/view.php?id=1614 Bug 1746: fuser output format clarification https://austingroupbugs.net/view.php?id=1746 Bug 1745: tsort input and output format clarifications https://austingroupbugs.net/view.php?id=1745 Any comments are due back before August 28 2023 regards Andrew Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 27th July 2023 Teleconference
All Enclosed are the minutes of yesterday’s meeting regards Andrew Minutes of the 27th July 2023 TeleconferenceAustin-1332 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 28th July 2023 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Apologies Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Tom Thompson, IEEE * General news The meeting on July 31 will be a webex. The meeting logistics for August 3rd are undecided as to whether it is a zoom or webex meeting. We will check with Nick on Monday. Andrew noted that draft planning is still to be done. It is expected that the cutoff for the next draft will be determined by the closing date for open interpretations. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1766: catgets: quotation in "Change History" lacks closing quotes Accepted https://austingroupbugs.net/view.php?id=1766 This item is tagged for TC3-2008. Bug 1769: CX shading needed for fputwc() EILSEQ error indicator requirement Accepted https://austingroupbugs.net/view.php?id=1769 Bug 1614: XSH 3/mktime does not specify EINVAL and should Accepted as Marked https://austingroupbugs.net/view.php?id=1614 An interpretation is required. Interpretation response: The standard clearly states that when an unsuccessful call to mktime() returns (time_t)-1 it sets errno to [EOVERFLOW], and conforming implementations must conform to this. Rationale: The RETURN VALUE section on the mktime() page states: If the time since the Epoch cannot be represented, the function shall return the value (time_t)-1 [CX]and set errno to indicate the error[/CX]. This requires that errno is set to indicate "the error", and the beginning of the sentence states the nature of the error condition to which "the error" refers: the time since the Epoch (i.e. the integer value to be returned) cannot be represented. The ERRORS section requires that the error number [EOVERFLOW] is used for this condition. Thus the standard requires that errno is set to [EOVERFLOW] when an unsuccessful call to mktime() returns (time_t)-1 and an implementation that sets it to [EINVAL] does not conform. The mktime() function does not have any way to indicate to the caller that an error other than [EOVERFLOW] occurred. Notes to the Editor (not part of this interpretation): On page 425 line 14451 section , after applying bug 1253 change: The value of tm_isdst shall be positive if Daylight Saving Time is in effect, 0 if Daylight Saving Time is not in effect, and negative if the information is not available. to: When tm_isdst is set by an interface defined in this standard, its value shall be positive if Daylight Saving Time (DST) is in effect and 0 if DST is not in effect. [CX]It shall not be set to a negative value by any interface defined in this standard. When tm_isdst is passed to the mktime() function, it specifies how mktime() is to handle DST when calculating the time since the Epoch value; see [xref to mktime()].[/CX] On page 1331 line 44310 section mktime(), delete: A positive or 0 value for tm_isdst shall cause mktime() to presume initially that Daylight Savings Time, respectively, is or is not in effect for the specified time. A negative value for tm_isdst shall cause mktime() to attempt to determine whether Daylight Savings Time is in effect for the specified time. On page 1331 line 44317 section mktime(), change: corrected for timezone and any seasonal time adjustments to: corrected for the offset of the timezone's standard time from Coordinated Universal Time and further corrected (if applicable--see below) for Daylight Saving Time After page 1331 line 44321 section mktime(), add these new paragraphs: [CX]If the timezone is one that includes Daylight Saving Time (DST) adjustments, the value of tm_isdst in the tm structure controls whether or not mktime() adjusts the calculated seconds since the Epoch value by the DST offset (after it has made the timezone adjustment), as follows: If tm_isdst is zero, mktime() shall not further adjust the seconds since the Epoch by the DST offset. If tm_isdst is positive, mktime() shall further adjust the seconds since the Epoch by the DST offset. If tm_isdst is negative, mktime() shall attempt to determine whether DST is in effect for the specified time; if it determines that DST is in effect it shall produce the same result as an equivalent call with a positive tm_isdst value, otherwise it shall produce the same result as an equivalent call
Minutes of the 24th July 2023 Teleconference
All Enclosed are the minutes of the Monday meeting this week regards Andrew --- Minutes of the 24th July 2023 TeleconferenceAustin-1331 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 25th July 2023 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Apologies Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Tom Thompson, IEEE * General news The meetings on July 27 will be webex meetings. The meeting on July 31 is undecided whether a zoom or webex. Andrew took an action to email Nick to check his availability to host a zoom call. Andrew confirmed he has submitted the ISO/IEC Organizational Representative report to SC22 for their September 2023 virtual meeting, and also the 1003.1 status report to the PASC SEC. Andrew has sent a position on the organization and style of the document to ISO/IEC who may question why it does not conform fully to their directives. This was supported by the SC22 chair. Andrew has prepared draft dispositions to the review comments from ISO and also IEEE. These have been circulated to the core team for initial review. We discussed draft planning and also whether we will need a PAR extension. We noted that we want to address low impact issues that are still open, including at least a revisit to the long term open issues. We noted that in some cases this will mean some triage on the items, with some being pushed to 202x-TC1 or left open still. Andrew has sent a status update to Tom Thompson, noting that the probability we will need a PAR extension has increased, as it is likely two more drafts will be needed. * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1743: mailx: revert faulty change Accepted https://austingroupbugs.net/view.php?id=1743 We discussed this during the 2023-07-24 conference call and found bugnote:6342 ambiguous. It sounds like the submitter is unhappy with the proposed changes in the note. We are backing out the changes made in issue 8 as suggested in the desired action and look forward to a new bug report to address the issues raised in the note. Bug 1744: Explicitly require killpg to be async-signal-safe Accepted https://austingroupbugs.net/view.php?id=1744 Bug 1748: Typo "define" s/b "defined". Accepted https://austingroupbugs.net/view.php?id=1748 This item is tagged for TC3-2008 Bug 1749: Special targets .PHONY and .NOTPARALLEL are not in alphabetic order Accepted https://austingroupbugs.net/view.php?id=1749 Bug 1750: typo: explictily Accepted https://austingroupbugs.net/view.php?id=1750 Bug 1752: replace "mantissa" by "significand" Accepted as Marked https://austingroupbugs.net/view.php?id=1752 Change, page 260, line 9115: the number of mantissa digits to: the number of digits in the significand Bug 1753: replace "mantissa" by "significand" Accepted https://austingroupbugs.net/view.php?id=1753 Bug 1754: formula for LDBL_MAX may be incorrect, e.g. for the double-double IBM format Accepted as Marked https://austingroupbugs.net/view.php?id=1754 On page 260 line 9123 section , change FUTURE DIRECTIONS from "None" to: The formula for calculating FLT_MAX, DBL_MAX, and LDBL_MAX is expected to change in the next revision of the ISO C standard such that it only applies if the values are normalized. Bug 1755: not deferring to C17 on specifics has knock-on effects Accepted https://austingroupbugs.net/view.php?id=1755 Bug 1757: expr: incorrectly describes BRE subexpression as "[\(...\)]" Accepted https://austingroupbugs.net/view.php?id=1757 This item is tagged for TC3-2008 Next Steps -- The next call is on: Thu 2023-07-27 (Webex meeting- general bugs/ballot resolution) Mon 2023-07-31 (TBD Zoom or Webex meeting - general bugs/ballot resolution) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Apologies in advance: Nick Stoughton 2023-07-27 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) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list logi
