Re: [Issue 8 drafts 0001603]: minor error in the pathname resolution

2022-08-30 Thread Oğuz via austin-group-l at The Open Group
31 Ağustos 2022 Çarşamba tarihinde Lawrence Velázquez via austin-group-l at
The Open Group  yazdı:
>
> Do lines 2857 through 2877 not address this sufficiently?


They do


-- 
Oğuz


Re: [Issue 8 drafts 0001603]: minor error in the pathname resolution

2022-08-30 Thread Lawrence Velázquez via austin-group-l at The Open Group
On Tue, Aug 30, 2022, at 7:34 PM, Austin Group Bug Tracker via austin-group-l 
at The Open Group wrote:
> Pathname resolution says:
> "A pathname that contains at least one non- character and that ends
> with one or more trailing  characters shall not be resolved
> successfully unless the last pathname component before the trailing 
> characters names an existing directory or a directory entry that is to be
> created for a directory immediately after the pathname is resolved."
>
> But shouldn't it also resolve successfully when the last pathname component
> before the trailing  characters names a symbolic link pointing to a
> existing directory?

Do lines 2857 through 2877 not address this sufficiently?

-- 
vq



[Issue 8 drafts 0001603]: minor error in the pathname resolution

2022-08-30 Thread Austin Group Bug Tracker via austin-group-l at The Open Group


A NOTE has been added to this issue. 
== 
https://www.austingroupbugs.net/view.php?id=1603 
== 
Reported By:calestyo
Assigned To:
== 
Project:Issue 8 drafts
Issue ID:   1603
Category:   Base Definitions and Headers
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: New
Name:   Christoph Anton Mitterer 
Organization:
User Reference:  
Section:4.14 Pathname Resolution 
Page Number:94 
Line Number:2850 ff 
Final Accepted Text: 
== 
Date Submitted: 2022-08-30 23:34 UTC
Last Modified:  2022-08-30 23:51 UTC
== 
Summary:minor error in the pathname resolution
== 

-- 
 (0005951) calestyo (reporter) - 2022-08-30 23:51
 https://www.austingroupbugs.net/view.php?id=1603#c5951 
-- 
(put one point into the wrong category in comment 0005950 ... so please
take the edited version from the website, not any email) 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-08-30 23:34 calestyo   New Issue
2022-08-30 23:34 calestyo   Name  => Christoph Anton
Mitterer
2022-08-30 23:34 calestyo   Section   => 4.14 Pathname
Resolution
2022-08-30 23:34 calestyo   Page Number   => 94  
2022-08-30 23:34 calestyo   Line Number   => 2850 ff 
2022-08-30 23:50 calestyo   Note Added: 0005950  
2022-08-30 23:51 calestyo   Note Edited: 0005950 
2022-08-30 23:51 calestyo   Note Added: 0005951  
==




[Issue 8 drafts 0001603]: minor error in the pathname resolution

2022-08-30 Thread Austin Group Bug Tracker via austin-group-l at The Open Group


A NOTE has been added to this issue. 
== 
https://www.austingroupbugs.net/view.php?id=1603 
== 
Reported By:calestyo
Assigned To:
== 
Project:Issue 8 drafts
Issue ID:   1603
Category:   Base Definitions and Headers
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: New
Name:   Christoph Anton Mitterer 
Organization:
User Reference:  
Section:4.14 Pathname Resolution 
Page Number:94 
Line Number:2850 ff 
Final Accepted Text: 
== 
Date Submitted: 2022-08-30 23:34 UTC
Last Modified:  2022-08-30 23:50 UTC
== 
Summary:minor error in the pathname resolution
== 

-- 
 (0005950) calestyo (reporter) - 2022-08-30 23:50
 https://www.austingroupbugs.net/view.php?id=1603#c5950 
-- 
I think there are further such cases:
- line 2840, "in the pathname fragment a/b, file b is located in directory
a", a might not be a directory, but also a symlink pointing to such

- 

Cases where I think it's really just directory:
- always when it says "directory entry"
- line 2839, "Each filename in the pathname is located in the directory
specified by its predecessor", because of the "specified" which a symlink
also does
- line 2875, "If the resulting pathname does not begin with a , the
predecessor of the first filename of the pathname is taken to be the
directory containing the symbolic link."... the predecessor could be a
symlink, so shouldn't it somehow say that it's taken to be the target of
such, if it is one?

Unsure:
- line 2842, "root directory of the process" ... I'd assume the process
root dir is always resolved already to a true directory?, just as the
current working directory in line 2845? ... Similar in line 2888

So better some expert check these :-) (thx) 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-08-30 23:34 calestyo   New Issue
2022-08-30 23:34 calestyo   Name  => Christoph Anton
Mitterer
2022-08-30 23:34 calestyo   Section   => 4.14 Pathname
Resolution
2022-08-30 23:34 calestyo   Page Number   => 94  
2022-08-30 23:34 calestyo   Line Number   => 2850 ff 
2022-08-30 23:50 calestyo   Note Added: 0005950  
==




[Issue 8 drafts 0001603]: minor error in the pathname resolution

2022-08-30 Thread Austin Group Bug Tracker via austin-group-l at The Open Group


The following issue has been SUBMITTED. 
== 
https://www.austingroupbugs.net/view.php?id=1603 
== 
Reported By:calestyo
Assigned To:
== 
Project:Issue 8 drafts
Issue ID:   1603
Category:   Base Definitions and Headers
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: New
Name:   Christoph Anton Mitterer 
Organization:
User Reference:  
Section:4.14 Pathname Resolution 
Page Number:94 
Line Number:2850 ff 
Final Accepted Text: 
== 
Date Submitted: 2022-08-30 23:34 UTC
Last Modified:  2022-08-30 23:34 UTC
== 
Summary:minor error in the pathname resolution
Description: 
Hey.

Pathname resolution says:
"A pathname that contains at least one non- character and that ends
with one or more trailing  characters shall not be resolved
successfully unless the last pathname component before the trailing 
characters names an existing directory or a directory entry that is to be
created for a directory immediately after the pathname is resolved."

But shouldn't it also resolve successfully when the last pathname component
before the trailing  characters names a symbolic link pointing to a
existing directory?

Not sure if one should also allow a dangling symlink if the directory is to
be created? I guess rather not because e.g.
$ ln -s non-existing dangling
$ mkdir -p dangling/sub

fails and probably should do so
Desired Action: 
In line 2852, after:
   "names an existing directory"
insert
   " or symbolic link that points to such"
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2022-08-30 23:34 calestyo   New Issue
2022-08-30 23:34 calestyo   Name  => Christoph Anton
Mitterer
2022-08-30 23:34 calestyo   Section   => 4.14 Pathname
Resolution
2022-08-30 23:34 calestyo   Page Number   => 94  
2022-08-30 23:34 calestyo   Line Number   => 2850 ff 
==