austin-group-l  

Messages by Thread

• Minutes of the 1st June 2020 Teleconference Andrew Josey
• Minutes of the 28th May 2020 Teleconference Andrew Josey
• [1003.1(2013)/Issue7+TC1 0000837]: renumber section 2.13 to be 2.6 in Issue 8 Austin Group Bug Tracker
  • [1003.1(2013)/Issue7+TC1 0000837]: renumber section 2.13 to be 2.6 in Issue 8 Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Austin Group Bug Tracker
  • RE: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined shwaresyst
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Stephane Chazelas
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Stephane Chazelas
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined shwaresyst
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Robert Elz
  • [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001347]: stderr access mode - "is expected to be" is not defined shwaresyst
• [1003.1(2016)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Larry Dwyer
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format J William Piggott
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Geoff Clare
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Joerg Schilling
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Larry Dwyer
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Larry Dwyer
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Alan Coopersmith
  • Re: [1003.1(2016)/Issue7+TC2 0001345]: date(1) default format Larry Dwyer
• Minutes of the 21st May 2020 Teleconference Andrew Josey
• Resizing anonymous memory objects Oskar Sveinsen
• [1003.1(2008)/Issue 7 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0000593]: posix_typed_mem_open requires the use of <fcntl.h> Austin Group Bug Tracker
• Minutes of the 18th May 2020 Teleconference Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001343]: The sh environment variable overview is missing OLDPWD Austin Group Bug Tracker
• Help request and introduction J William Piggott
  • Re: Help request and introduction Geoff Clare
  • Re: Help request and introduction J William Piggott
  • RE: [EXTERNAL] Re: Help request and introduction Jason Zions
  • Re: Help request and introduction J William Piggott
  • Re: Help request and introduction shwaresyst
• Minutes of the 14th May 2020 Teleconference Andrew Josey
• setresuid() and friends for next major revision? Michael Kerrisk
• Minutes of the 11th May 2020 Teleconference Andrew Josey
• Use of Zoom for Austin Group meetings Nick Stoughton
• Interpretation starting for a 30 day review (1340) Andrew Josey
• Minutes of the 7th May 2020 Teleconference Andrew Josey
• Minutes of the 4th May 2020 Teleconference Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001342]: Aliases in command substitutions are handled differently when the command subst is quoted vs not quoted Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001342]: Aliases in command substitutions are handled differently when the command subst is quoted vs not quoted Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001342]: Aliases in command substitutions are handled differently when the command subst is quoted vs not quoted Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001342]: Aliases in command substitutions are handled differently when the command subst is quoted vs not quoted Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001342]: Aliases in command substitutions are handled differently when the command subst is quoted vs not quoted Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001342]: Aliases in command substitutions are handled differently when the command subst is quoted vs not quoted Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Geoff Clare
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Casper . Dik
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect shwaresyst
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect shwaresyst
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Casper . Dik
  • Re: [1003.1(2016)/Issue7+TC2 0001341]: The resolution of bugid:1208 as amended by bugnote:4830 is incorrect Robert Elz
• [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Geoff Clare
  • Re: [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Robert Elz
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001340]: PATH specification has an ambiguity. Austin Group Bug Tracker
• [Online Pubs 0001339]: bzip2 download has not been updated Austin Group Bug Tracker
  • [Online Pubs 0001339]: bzip2 download has not been updated Austin Group Bug Tracker
• [Online Pubs 0001338]: creat and open have similar missing BR element between includes Austin Group Bug Tracker
  • [Online Pubs 0001338]: creat and open have similar missing BR element between includes Austin Group Bug Tracker
• Minutes of the 30th April 2020 Teleconference Andrew Josey
• Interpretation starting for a 30 day review (1328) Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001328]: posix_spawn lacks use of restrict Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001328]: posix_spawn lacks use of restrict Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001328]: posix_spawn lacks use of restrict Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001328]: posix_spawn lacks use of restrict Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001328]: posix_spawn lacks use of restrict Austin Group Bug Tracker
• Interpretation starting for a 30 day review (1317) Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001337]: Clarify socket option values after accept() Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001337]: Clarify socket option values after accept() Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001337]: Clarify socket option values after accept() Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001337]: Clarify socket option values after accept() Austin Group Bug Tracker
• Minutes of the 27th April 2020 Teleconference Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001154]: Add 'rm -v' Austin Group Bug Tracker
• Minutes of the 23rd April 2020 Teleconference Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001141]: Add WCOREDUMP(stat) to sys/wait.h Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001053]: Add a "size" mode to stty(1) Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001139]: require RE \] to match ] when outside bracket expressions Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001336]: getrusage should recursively include information about children of children Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001133]: find clarification on -xdev behavior for mounted filesystem within primary Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001112]: mutex/rwlock ownership after fork is unclear Austin Group Bug Tracker
• Minutes of the 20th April 2020 Teleconference Andrew Josey
• [1003.1(2008)/Issue 7 0001073]: dirname utility: algorithm for computing pathname string is stricter than the corresponding dirname() function Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001102]: inet_addr() cannot parse 255.255.255.255. Mark it as obsolete, add inet_aton(), or both? Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001101]: inet_ntoa(): superfluous and not thread-safe. Mark as [OB] for issue 8? Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001076]: Cancellation Points Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001071]: Name space reservation should move to XBD Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001070]: Collation issues in XCU (changes for Issue 8) Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001067]: missing socket() error for unsupported socket type Austin Group Bug Tracker
• [Online Pubs 0001335]: Missing newline or BR element on fstatat() page Austin Group Bug Tracker
  • [Online Pubs 0001335]: Missing newline or BR element on fstatat() page Austin Group Bug Tracker
  • [Online Pubs 0001335]: Missing newline or BR element on fstatat() page Austin Group Bug Tracker
  • [Online Pubs 0001335]: Missing newline or BR element on fstatat() page Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001335]: Missing newline or BR element on fstatat() page Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001335]: Missing newline or BR element on fstatat() page Austin Group Bug Tracker
• sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Harald van Dijk
  • Re: sh: aliases in command substitutions Robert Elz
  • RE: aliases in command substitutions Schwarz, Konrad
  • Re: aliases in command substitutions Robert Elz
  • Re: aliases in command substitutions Chet Ramey
  • Re: aliases in command substitutions Robert Elz
  • RE: aliases in command substitutions Schwarz, Konrad
  • RE: aliases in command substitutions Schwarz, Konrad
  • Re: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Joseph Myers
  • Re: sh: aliases in command substitutions shwaresyst
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Don Cragun
  • Re: sh: aliases in command substitutions Joseph Myers
  • Re: sh: aliases in command substitutions Donn Terry
  • Re: sh: aliases in command substitutions shwaresyst
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions shwaresyst
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions shwaresyst
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions shwaresyst
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions shwaresyst
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions Joerg Schilling
  • Re: sh: aliases in command substitutions Chet Ramey
  • Re: sh: aliases in command substitutions Robert Elz
  • Re: sh: aliases in command substitutions Chet Ramey
• XCU 2.14: Exit status by no-argument `return' in shell trap handlers Koichi Murase
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Oğuz
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Oğuz
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Koichi Murase
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Oğuz
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Robert Elz
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Harald van Dijk
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Koichi Murase
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Harald van Dijk
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Koichi Murase
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Robert Elz
  • Re: XCU 2.14: Exit status by no-argument `return' in shell trap handlers Koichi Murase
• Minutes of the 16th April 2020 Teleconference Andrew Josey
• Bug 1016: is anybody working on adding O_NOCLOBBER? Geoff Clare
  • RE: Bug 1016: is anybody working on adding O_NOCLOBBER? shwaresyst
• [1003.1(2008)/Issue 7 0001064]: basename() and dirname(): Specification is not complete enough to allow existing thread-unsafe implementations Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0001056]: CMSG_NXTHDR(): under what criteria may NULL be returned? Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001056]: CMSG_NXTHDR(): under what criteria may NULL be returned? Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0001054]: stdio.h doesn't allow FILE to be opaque? Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001047]: Unspecified behaviour for cd "" causes a safety issue Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001044]: Calling setsid as part of posix_spawn Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001041]: Encourage implementations to include better integrity checksum, compression and decompression utilities if possible. Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0001033]: LOG_UPTO(): Present on all (?) systems, but not standardized? Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001031]: Add -iname (case-insensitive name search) to the find utility. Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001027]: file-position indicator for open_wmemstream() streams Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001023]: Behaviour of ls -R without -a under presence of directories beginning with a dot Austin Group Bug Tracker
• pwd(1) pwd -L and multple adjacent slashes in $PWD, Casper . Dik

• Earlier messages