Minutes of the 13th August 2020 Teleconference
All
Enclosed are the minutes of the thursday call this week.
As a reminder there are no meetings on Mon 2020-08-17, Mon 2020-08-31, Mon
2020-09-07
The next call is August 20th .
regards
Andrew
--
Minutes of the 13th August 2020 Teleconference Austin-1053 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 15th August 2020
Attendees:
Nick Stoughton, 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
Joerg Schilling, FOKUS Fraunhofer
Geoff Clare, The Open Group
Andrew Josey, The Open Group
Richard Hansen
Tom Thompson, IEEE
* General news
We discussed an issue Nick had raised about ISO C and use of consts
(changing char * to const char *). There is a document being prepared
as a response to the ISO C committee.
N2526 document http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2526.htm
Draft response:
https://docs.google.com/document/d/1lgITI8PhAQk6ox6OjsrJK65WjykH47Kua74CusjswFE/edit?usp=sharing
We noted the terminology usage discussion is still running on the list.
A reminder that the Draft 1 review is now underway and runs until
August 25 2020. The draft can be obtained from the login page of
the Austin Group at: https://www.opengroup.org/austin/login.html .
* Outstanding actions
(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)
Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR
list" OPEN
https://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.
Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.
Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface,
referencing bug note 4478.
* Current Business
Gettext draft.
We continued this discussion and will continue on the next call.
The gettext draft in the etherpad is at
https://posix.rhansen.org/p/gettext_draft
https://posix.rhansen.org/p/gettext_split
Next Steps
--
There are no meetings on Mon 2020-08-17, Mon 2020-08-31, Mon 2020-09-07
The next calls are on:
August 20th 2020 (Thursday)
This call will be for 90 minutes.
Aug 24th 2020 (Monday)
This call will be for 60 minutes.
Apologies in advance:
None
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
username={first part of hostname} password=2115756#
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&listid=2481
[1003.1(2016)/Issue7+TC2 0001392]: find(1): clarify whether -perm ops - and + should follow chmod
The following issue has been SUBMITTED. == https://austingroupbugs.net/view.php?id=1392 == Reported By:mohd_akram Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1392 Category: Shell and Utilities Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: Mohamed Akram Organization: User Reference: Section:find Page Number:2797 Line Number:91951-91956 Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-14 12:55 UTC Last Modified: 2020-08-14 12:55 UTC == Summary:find(1): clarify whether -perm ops - and + should follow chmod Description: Currently, BSD/macOS find(1) behave like chmod when it comes to the - and + operators of -perm: $ umask 0022 $ touch file $ chmod +w file $ find file -perm -+w file GNU find behaves differently (https://savannah.gnu.org/bugs/?58654): $ umask 0002 $ touch file $ chmod +w $ find file -perm -+w GNU find treats = and + as equivalent, while BSD find doesn't (which is IMO more useful). Desired Action: Clarify the behavior of find(1) -perm with respect to the - and + operators. == Issue History Date ModifiedUsername FieldChange == 2020-08-14 12:55 mohd_akram New Issue 2020-08-14 12:55 mohd_akram Name => Mohamed Akram 2020-08-14 12:55 mohd_akram Section => find 2020-08-14 12:55 mohd_akram Page Number => 2797 2020-08-14 12:55 mohd_akram Line Number => 91951-91956 ==
[1003.1(2016)/Issue7+TC2 0001389]: Shell command search procedure is incorrect
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1389 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1389 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:2.9.1.1 1.c (2.9.1.4 1.c in Issue8 Draft 1), 2.9.1.1 1.d, 2.9.1.1 1.e.i.a Page Number:2367 (2335 in Issue8 draft 1) Line Number:75564-73 75577-78 (74159-64 74168-71 in Issue8 draft 1) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:52 UTC Last Modified: 2020-08-14 10:39 UTC == Summary:Shell command search procedure is incorrect == Relationships ID Summary -- duplicate of854 requirement for additional built-in uti... related to 0001390 No method to invoke a non-standard buil... related to 0001391 Unclear language in specification of ut... == -- (0004924) joerg (reporter) - 2020-08-14 10:39 https://www.austingroupbugs.net/view.php?id=1389#c4924 -- Just in case this is not known, ksh93 implements PATH search for builtin commands and this was a requirement for ksh93 integration into OpenSolaris in 2008 after a long and heaty discussion. The reason for that requirement was to retain POSIX compliance even though basicstandard utilities are built into the standard shell. If a shell does not implement PATH search for additional builtins, we would need to forbid shells to add more builtins than the minimal set. ksh93 added many additional builtins like cat, chown, cmp, ... and POSIX grants that a user that if he has private version of system utilities, the shell needs to use them if they are first in PATH. If a shell adds more builtins than currently documented, this would no longer work as historically builtin are always found first. As a consequence, we created a list of tainted utilities see bug:854, that already may be builtins. If you like to add more builtins from the list of standard utilities, you either need to implement PATH search for these builtins, or you are forbidden to implement these utilities as builtins. In ksh93, builtin commands are managed with the builtin named "builtin". Call builtin for a liste.g. builtin : . [ /bin/cat /bin/chown /bin/cksum /bin/cmp /bin/comm /bin/cut /bin/dirname /bin/fold /bin/getconf /bin/head /bin/join /bin/logname /bin/mkdir /bin/mkfifo /bin/mktemp /bin/paste /bin/pathchk /bin/rev /bin/rmdir /bin/sum /bin/sync /bin/tail /bin/tee /bin/tty /bin/uniq /bin/wc /bin/xgrep /sbin/sync /usr/ast/bin/basename /usr/ast/bin/cat /usr/ast/bin/chgrp /usr/ast/bin/chmod /usr/ast/bin/chown /usr/ast/bin/cksum /usr/ast/bin/cmp /usr/ast/bin/comm /usr/ast/bin/cp /usr/ast/bin/cut /usr/ast/bin/date /usr/ast/bin/dirname /usr/ast/bin/egrep /usr/ast/bin/expr /usr/ast/bin/fds /usr/ast/bin/fgrep /usr/ast/bin/fmt /usr/ast/bin/fold /usr/ast/bin/grep /usr/ast/bin/head /usr/ast/bin/id /usr/ast/bin/join /usr/ast/bin/ln /usr/ast/bin/logname /usr/ast/bin/md5sum /usr/ast/bin/mkdir /usr/ast/bin/mkfifo /usr/ast/bin/mktemp /usr/ast/bin/mv /usr/ast/bin/paste /usr/ast/bin/pathchk /usr/ast/bin/readlink /usr/ast/bin/rev /usr/ast/bin/rm /usr/ast/bin/rmdir /usr/ast/bin/stty /usr/ast/bin/sum /usr/ast/bin/sync /usr/ast/bin/tail /usr/ast/bin/tee /usr/ast/bin/tty /usr/ast/bin/uname /usr/ast/bin/uniq /usr/ast/bin/wc /usr/ast/bin/xgrep /usr/sbin/sync /usr/xpg4/bin/basename /usr/xpg4/bin/egrep /usr/xpg4/bin/fgrep /usr/xpg4/bin/grep /usr/xpg4/bin/id /usr/xpg4/bin/rm /usr/xpg4/bin/tail /usr/xpg6/bin/expr alarm alias bg break builtin cd command Note that the builtins bound to /usr/ast/bin are not fully POSIX compliant and there fore are not bound to a path that appears in the default PATH. If you do not care about POSIX compliance or if you do not like to add more builtins to your shell, you may do what ever you like. If you however like to add more builtins, you need to follow long existing rules about PATH s
Re: [1003.1(2008)/Issue 7 0001387]: Should EAGAIN be acceptable for malloc failure?
>-- >Re:bugnote: 4916 > >Hi Alan, do you know where EAGAIN is created in the Solaris kernel while >running sbrk()? Not Alan; but EAGAIN when anon_resv() fails. (anon_resv tries to allocate space in swapfs). ENOMEM is generally returned when we run into limits: out of VM or into resource control limits in Solaris. Casper
[1003.1(2008)/Issue 7 0001387]: Should EAGAIN be acceptable for malloc failure?
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1387 == Reported By:rhansen Assigned To:ajosey == Project:1003.1(2008)/Issue 7 Issue ID: 1387 Category: System Interfaces Type: Clarification Requested Severity: Editorial Priority: normal Status: Under Review Name: Richard Hansen Organization: User Reference: Section:malloc Page Number:1295 (Issue 7 2018 edition) Line Number:43161 (Issue 7 2018 edition) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-10 16:46 UTC Last Modified: 2020-08-14 09:50 UTC == Summary:Should EAGAIN be acceptable for malloc failure? == -- (0004923) joerg (reporter) - 2020-08-14 09:50 https://www.austingroupbugs.net/view.php?id=1387#c4923 -- Re:bugnote: 4916 Hi Alan, do you know where EAGAIN is created in the Solaris kernel while running sbrk()? Due to the object oriented design of the address space administration in SunOS, it is hard to find the right location in the code. What I however can say is that since SunOS-4.0 (from late 1987), kmem_alloc() with a flag of KM_NOSLEEP return EAGAIN in case that the operation would result in a sleep. The anon pages segment driver vm_anon.c however only returns ENOMEM, the sgvn driver seg_vn.c returns ENOMEM in plenty of cases (e.g. with shared mappings that are not expected to apply to sbrk()), but also ENOMEM in other cases. Issue History Date ModifiedUsername FieldChange == 2020-08-10 16:46 rhansenNew Issue 2020-08-10 16:46 rhansenStatus New => Under Review 2020-08-10 16:46 rhansenAssigned To => ajosey 2020-08-10 16:46 rhansenName => Richard Hansen 2020-08-10 16:46 rhansenSection => malloc 2020-08-10 16:46 rhansenPage Number => 1295 (Issue 7 2018 edition) 2020-08-10 16:46 rhansenLine Number => 43161 (Issue 7 2018 edition) 2020-08-10 16:46 rhansenInterp Status => --- 2020-08-10 17:09 rhansenNote Added: 0004914 2020-08-10 17:14 rhansenDescription Updated 2020-08-10 17:35 rhansenDesired Action Updated 2020-08-10 17:36 rhansenDesired Action Updated 2020-08-10 17:39 Don Cragun Note Added: 0004915 2020-08-10 17:45 alanc Note Added: 0004916 2020-08-10 17:45 alanc Note Edited: 0004916 2020-08-11 01:08 shware_systems Note Added: 0004918 2020-08-14 09:50 joerg Note Added: 0004923 ==
[1003.1(2016)/Issue7+TC2 0001391]: Unclear language in specification of utilities implemented as functions
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1391 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1391 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:2.9.1.1 1.c (2.9.1.4 1.c in Issue 8 draft 1) Page Number:2367 (2294 in Issue 8 draft 1) Line Number:75564-7 (74159-62 in Issue 8 draft 1) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:58 UTC Last Modified: 2020-08-14 09:21 UTC == Summary:Unclear language in specification of utilities implemented as functions == Relationships ID Summary -- related to 0001390 No method to invoke a non-standard buil... related to 0001389 Shell command search procedure is incor... == -- (0004922) geoffclare (manager) - 2020-08-14 09:21 https://austingroupbugs.net/view.php?id=1391#c4922 -- I think there is a misunderstanding here of what "If the implementation has provided a standard utility in the form of a function" means. The description talks about "if the shell did implement some standard utility as a function" which has implications that are not quite the same. I believe the thinking behind "the implementation has provided a standard utility in the form of a function" is that an implementation could define a function in an implementation-provided shell startup file. Some implementations do this with aliases (such as the misguided alias rm='rm -i'); the standard allows a similar thing with functions. I suppose a function could also be predefined internally by the shell itself. However, the crucial thing is that it is just a function definition like any other; it is not special (other than being already defined by the time the shell reads commands from the user/script). So if the application defines a function of the same name, it simply replaces the one provided by the implementation. The application could also delete the function using "unset -f". I think a suitable change to clarify this would be to change:If the implementation has provided a standard utility in the form of a function, it shall not be recognized at this point.to:If the implementation has provided a standard utility in the form of a function, and that function definition still exists (i.e. has not been removed using unset -f or replaced via another function definition with the same name), it shall not be recognized at this point. Issue History Date ModifiedUsername FieldChange == 2020-08-13 19:58 kreNew Issue 2020-08-13 19:58 kreName => Robert Elz 2020-08-13 19:58 kreSection => 2.9.1.1 1.c (2.9.1.4 1.c in Issue 8 draft 1) 2020-08-13 19:58 krePage Number => 2367 (2294 in Issue 8 draft 1) 2020-08-13 19:58 kreLine Number => 75564-7 (74159-62 in Issue 8 draft 1) 2020-08-13 21:18 Don Cragun Relationship added related to 0001389 2020-08-13 21:19 Don Cragun Relationship added related to 0001390 2020-08-14 08:31 geoffclare Interp Status => --- 2020-08-14 08:31 geoffclare Description Updated 2020-08-14 09:21 geoffclare Note Added: 0004922 ==
[1003.1(2016)/Issue7+TC2 0001390]: No method to invoke a non-standard built-in utility
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1390 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1390 Category: Shell and Utilities Type: Omission Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:XCU 2.9.1.1 (In Issue 8 draft 1, section 2.9.1.4) Page Number:2367-8 (in Issue 8 draft 1: 2293-4) Line Number:75545-75627 (In Issue 8 Draft 1, lines 74140-74183) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:54 UTC Last Modified: 2020-08-14 09:01 UTC == Summary:No method to invoke a non-standard built-in utility == Relationships ID Summary -- related to 0001389 Shell command search procedure is incor... related to 0001391 Unclear language in specification of ut... == -- (0004921) geoffclare (manager) - 2020-08-14 09:01 https://austingroupbugs.net/view.php?id=1390#c4921 -- "The standard as currently written provides no mechanism to allow such non-standard built-in utilities to be invoked." This was solved in Issue 8 draft 1 by allowing implementations to add to the list of intrinsic utilities. See XCU 1.7 (P2268 L73117) in the draft: "Whether any additional utility is considered an intrinsic utility is implementation-defined." All the implementation needs to do is document the additions. This practice is not recommended (through the use of "should not" on L73119) but is allowed. Issue History Date ModifiedUsername FieldChange == 2020-08-13 19:54 kreNew Issue 2020-08-13 19:54 kreName => Robert Elz 2020-08-13 19:54 kreSection => XCU 2.9.1.1 (In Issue 8 draft 1, section 2.9.1.4) 2020-08-13 19:54 krePage Number => 2367-8 (in Issue 8 draft 1: 2293-4) 2020-08-13 19:54 kreLine Number => 75545-75627 (In Issue 8 Draft 1, lines 74140-74183) 2020-08-13 21:17 Don Cragun Relationship added related to 0001389 2020-08-13 21:19 Don Cragun Relationship added related to 0001391 2020-08-14 08:30 geoffclare Interp Status => --- 2020-08-14 08:30 geoffclare Description Updated 2020-08-14 09:01 geoffclare Note Added: 0004921 ==
[1003.1(2013)/Issue7+TC1 0000854]: requirement for additional built-in utilities to be searched for via $PATH was not and is not existing practice
The issue 0001389 has been set as DUPLICATE OF the following issue. == https://austingroupbugs.net/view.php?id=854 == Reported By:philip-guenther Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 854 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: Applied Name: Philip Guenther Organization: OpenBSD User Reference: Section:XCU 2.9.1.1 Page Number:2339 Line Number:74397-74398 Interp Status: Approved Final Accepted Text:See https://austingroupbugs.net/view.php?id=854#c2495 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2014-07-02 07:29 UTC Last Modified: 2020-03-27 17:22 UTC == Summary:requirement for additional built-in utilities to be searched for via $PATH was not and is not existing practice == Relationships ID Summary -- related to 705 Add hash, type and ulimit to regular bu... has duplicate 0001389 Shell command search procedure is incor... related to 901 reserve _POSIX* shell option namespace ... related to 654 unclear behavior of in-line variable as... == Issue History Date ModifiedUsername FieldChange == 2014-07-02 07:29 philip-guentherNew Issue 2014-07-02 07:29 philip-guentherName => Philip Guenther 2014-07-02 07:29 philip-guentherOrganization => OpenBSD 2014-07-02 07:29 philip-guentherSection => XCU 2.9.1.1 2014-07-02 07:29 philip-guentherPage Number => 2339 2014-07-02 07:29 philip-guentherLine Number => 74397-74398 2014-12-01 06:39 Don Cragun Note Added: 0002453 2014-12-01 06:46 Don Cragun Note Edited: 0002453 2014-12-01 06:53 Don Cragun Note Edited: 0002453 2014-12-01 06:57 Don Cragun Note Edited: 0002453 2014-12-01 07:01 Don Cragun Interp Status => --- 2014-12-01 07:01 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=854#c2453. 2014-12-01 07:01 Don Cragun Tag Attached: issue8 2014-12-01 07:17 wpollock Note Added: 0002454 2014-12-01 07:34 Don Cragun Note Edited: 0002453 2014-12-01 07:36 Don Cragun Note Added: 0002455 2014-12-04 07:56 Don Cragun Note Edited: 0002453 2014-12-04 07:56 Don Cragun Note Edited: 0002455 2014-12-04 08:17 Don Cragun Note Edited: 0002453 2014-12-04 08:18 Don Cragun Note Edited: 0002453 2014-12-04 08:21 Don Cragun Note Edited: 0002455 2014-12-04 08:23 Don Cragun Note Edited: 0002453 2014-12-04 08:24 Don Cragun Note Edited: 0002455 2014-12-04 16:18 Don Cragun Note Edited: 0002453 2014-12-04 16:33 Don Cragun Note Edited: 0002453 2014-12-05 08:37 rhansenNote Added: 0002477 2014-12-05 08:39 rhansenNote Edited: 0002477 2014-12-05 08:42 rhansenNote Edited: 0002477 2014-12-05 08:43 rhansenNote Edited: 0002477 2014-12-05 14:03 chet_ramey Note Added: 0002479 2014-12-06 22:51 Don Cragun Note Added: 0002487 2014-12-06 22:54 Don Cragun Note Edited: 0002487 2014-12-06 23:01 Don Cragun Note Edited: 0002487 2014-12-06 23:01 Don Cragun Note View State: public: 2487 2014-12-08 15:03 Don Cragun Note Edited: 0002487 2014-12-11 16:21 nick Relatio
[1003.1(2016)/Issue7+TC2 0001389]: Shell command search procedure is incorrect
The following issue has been set as DUPLICATE OF issue 854. == https://austingroupbugs.net/view.php?id=1389 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1389 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:2.9.1.1 1.c (2.9.1.4 1.c in Issue8 Draft 1), 2.9.1.1 1.d, 2.9.1.1 1.e.i.a Page Number:2367 (2335 in Issue8 draft 1) Line Number:75564-73 75577-78 (74159-64 74168-71 in Issue8 draft 1) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:52 UTC Last Modified: 2020-08-14 08:47 UTC == Summary:Shell command search procedure is incorrect == Relationships ID Summary -- duplicate of854 requirement for additional built-in uti... related to 0001390 No method to invoke a non-standard buil... related to 0001391 Unclear language in specification of ut... == Issue History Date ModifiedUsername FieldChange == 2020-08-13 19:52 kreNew Issue 2020-08-13 19:52 kreName => Your Name Here 2020-08-13 19:52 kreSection => (section number or name, can be interface name) 2020-08-13 19:52 krePage Number => (page or range of pages) 2020-08-13 19:52 kreLine Number => 75564-73 75577-78 (74159-64 74168-71 in Issue8 draft 1) 2020-08-13 21:17 Don Cragun Name Your Name Here => Robert Elz 2020-08-13 21:17 Don Cragun Interp Status => --- 2020-08-13 21:17 Don Cragun Relationship added related to 0001390 2020-08-13 21:18 Don Cragun Relationship added related to 0001391 2020-08-13 21:24 Don Cragun Severity Editorial => Objection 2020-08-13 21:24 Don Cragun Type Clarification Requested => Error 2020-08-13 21:30 Don Cragun Section (section number or name, can be interface name) => 2.9.1.1 1.c (2.9.1.4 1.c in Issue8 Draft 1), 2.9.1.1 1.d, 2.9.1.1 1.e.i.a 2020-08-13 21:30 Don Cragun Page Number (page or range of pages) => 2367 (2335 in Issue8 draft 1) 2020-08-14 08:47 geoffclare Note Added: 0004920 2020-08-14 08:47 geoffclare Relationship added duplicate of 854 ==
[1003.1(2016)/Issue7+TC2 0001389]: Shell command search procedure is incorrect
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1389 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1389 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:2.9.1.1 1.c (2.9.1.4 1.c in Issue8 Draft 1), 2.9.1.1 1.d, 2.9.1.1 1.e.i.a Page Number:2367 (2335 in Issue8 draft 1) Line Number:75564-73 75577-78 (74159-64 74168-71 in Issue8 draft 1) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:52 UTC Last Modified: 2020-08-14 08:47 UTC == Summary:Shell command search procedure is incorrect == Relationships ID Summary -- related to 0001390 No method to invoke a non-standard buil... related to 0001391 Unclear language in specification of ut... == -- (0004920) geoffclare (manager) - 2020-08-14 08:47 https://austingroupbugs.net/view.php?id=1389#c4920 -- Although it goes into more detail, this is effectively a repeat of bug https://austingroupbugs.net/view.php?id=854 and should be closed as a duplicate. Issue History Date ModifiedUsername FieldChange == 2020-08-13 19:52 kreNew Issue 2020-08-13 19:52 kreName => Your Name Here 2020-08-13 19:52 kreSection => (section number or name, can be interface name) 2020-08-13 19:52 krePage Number => (page or range of pages) 2020-08-13 19:52 kreLine Number => 75564-73 75577-78 (74159-64 74168-71 in Issue8 draft 1) 2020-08-13 21:17 Don Cragun Name Your Name Here => Robert Elz 2020-08-13 21:17 Don Cragun Interp Status => --- 2020-08-13 21:17 Don Cragun Relationship added related to 0001390 2020-08-13 21:18 Don Cragun Relationship added related to 0001391 2020-08-13 21:24 Don Cragun Severity Editorial => Objection 2020-08-13 21:24 Don Cragun Type Clarification Requested => Error 2020-08-13 21:30 Don Cragun Section (section number or name, can be interface name) => 2.9.1.1 1.c (2.9.1.4 1.c in Issue8 Draft 1), 2.9.1.1 1.d, 2.9.1.1 1.e.i.a 2020-08-13 21:30 Don Cragun Page Number (page or range of pages) => 2367 (2335 in Issue8 draft 1) 2020-08-14 08:47 geoffclare Note Added: 0004920 ==
Re: Did I ever say how much I detest mantis...
Robert Elz wrote, on 14 Aug 2020: > > Any chance that you could also correct 1390 and 1391 and change > bug:1389 into bugid:1389 so that the auto link generation works > (that one being wrong is entirely my fault, I forgot to check the > correct method). I have made these changes. -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
[1003.1(2016)/Issue7+TC2 0001391]: Unclear language in specification of utilities implemented as functions
The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1391 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1391 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:2.9.1.1 1.c (2.9.1.4 1.c in Issue 8 draft 1) Page Number:2367 (2294 in Issue 8 draft 1) Line Number:75564-7 (74159-62 in Issue 8 draft 1) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:58 UTC Last Modified: 2020-08-14 08:31 UTC == Summary:Unclear language in specification of utilities implemented as functions == Relationships ID Summary -- related to 0001390 No method to invoke a non-standard buil... related to 0001389 Shell command search procedure is incor... == Issue History Date ModifiedUsername FieldChange == 2020-08-13 19:58 kreNew Issue 2020-08-13 19:58 kreName => Robert Elz 2020-08-13 19:58 kreSection => 2.9.1.1 1.c (2.9.1.4 1.c in Issue 8 draft 1) 2020-08-13 19:58 krePage Number => 2367 (2294 in Issue 8 draft 1) 2020-08-13 19:58 kreLine Number => 75564-7 (74159-62 in Issue 8 draft 1) 2020-08-13 21:18 Don Cragun Relationship added related to 0001389 2020-08-13 21:19 Don Cragun Relationship added related to 0001390 2020-08-14 08:31 geoffclare Interp Status => --- 2020-08-14 08:31 geoffclare Description Updated ==
[1003.1(2016)/Issue7+TC2 0001390]: No method to invoke a non-standard built-in utility
The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1390 == Reported By:kre Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1390 Category: Shell and Utilities Type: Omission Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section:XCU 2.9.1.1 (In Issue 8 draft 1, section 2.9.1.4) Page Number:2367-8 (in Issue 8 draft 1: 2293-4) Line Number:75545-75627 (In Issue 8 Draft 1, lines 74140-74183) Interp Status: --- Final Accepted Text: == Date Submitted: 2020-08-13 19:54 UTC Last Modified: 2020-08-14 08:30 UTC == Summary:No method to invoke a non-standard built-in utility == Relationships ID Summary -- related to 0001389 Shell command search procedure is incor... related to 0001391 Unclear language in specification of ut... == Issue History Date ModifiedUsername FieldChange == 2020-08-13 19:54 kreNew Issue 2020-08-13 19:54 kreName => Robert Elz 2020-08-13 19:54 kreSection => XCU 2.9.1.1 (In Issue 8 draft 1, section 2.9.1.4) 2020-08-13 19:54 krePage Number => 2367-8 (in Issue 8 draft 1: 2293-4) 2020-08-13 19:54 kreLine Number => 75545-75627 (In Issue 8 Draft 1, lines 74140-74183) 2020-08-13 21:17 Don Cragun Relationship added related to 0001389 2020-08-13 21:19 Don Cragun Relationship added related to 0001391 2020-08-14 08:30 geoffclare Interp Status => --- 2020-08-14 08:30 geoffclare Description Updated ==
