Re: pathnames with two leading slashes

Hi Cris, Please find comments in-line below... > On Jul 31, 2023, at 4:05 PM, Christoph Anton Mitterer via austin-group-l at > The Open Group wrote: > > Hey. > > POSIX 4.13 Pathname Resolution says: >> If a pathname begins with two successive characters, the >> first component following the

pathnames with two leading slashes

Hey. POSIX 4.13 Pathname Resolution says: > If a pathname begins with two successive characters, the > first component following the leading characters may be > interpreted in an implementation-defined manner, although more than > two leading characters shall be treated as a single >

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?

[1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC?

The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1674 == Reported By:eblake Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001732]: cp and mv EXIT STATUS does not account for -i

The following issue has been UPDATED. == https://www.austingroupbugs.net/view.php?id=1732 == Reported By:geoffclare Assigned To:

[Issue 8 drafts 0001649]: Field splitting is woefully under specified, and in places, simply wrong

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1649 == Reported By:kre Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC?

The following issue NEEDS AN INTERPRETATION. == https://austingroupbugs.net/view.php?id=1674 == Reported By:eblake Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC?

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1674 == Reported By:eblake Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001725]: mailx: *screen*: specify default

The following issue has been RESOLVED. == https://www.austingroupbugs.net/view.php?id=1725 == Reported By:steffen Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001728]: typo on the getprotobyname() pointer page

The following issue has been RESOLVED. == https://www.austingroupbugs.net/view.php?id=1728 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001729]: mkdir() ENOENT and ENOTDIR overlap

The following issue has been RESOLVED. == https://www.austingroupbugs.net/view.php?id=1729 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001730]: m4 synopsis does not show file operand as optional

The following issue has been RESOLVED. == https://www.austingroupbugs.net/view.php?id=1730 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001731]: pthread_sigmask() pending signal requirement time paradox

The following issue has been RESOLVED. == https://www.austingroupbugs.net/view.php?id=1731 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001732]: cp and mv EXIT STATUS does not account for -i

The following issue NEEDS AN INTERPRETATION. == https://www.austingroupbugs.net/view.php?id=1732 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001732]: cp and mv EXIT STATUS does not account for -i

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1732 == Reported By:geoffclare Assigned To: