Re: [Fwd: [bug #6047] rm -f "" prints diagnostic message under the Hurd]

[Marcus Brinkmann]

At Fri, 30 Apr 2004 13:35:14 +0300,
Ognyan Kulev wrote:
> 
> Ognyan Kulev wrote:
> > Ognyan Kulev wrote:
> >> [ENOENT]
> >>     No such file or directory. A component of a specified pathname 
> >> does not exist, or the pathname is an empty string.
> >>
> >> Again, the easiest is to make diskfs_lookup return ENOENT when empty 
> >> string is given.  Or we can change dir_* functions, which is not hard. 
> >> glibc can be changed too, but I suppose we want Hurd RPCs to have the 
> >> POSIX behaviour.
> > 
> > For completeness, it should be noted that name passed to diskfs_lookup 
> > and dir_* is pathname component, not whole pathname.  The ENOENT error 
> > in POSIX is about whole pathname being empty string.  So if glibc is 
> > changed to handle empty pathnames and diskfs is not touched, we'll 
> > become POSIX-compliant (in handling empty pathnames).
> 
> In what way to fix the bug?  Currently, I'm mostly inclined to change 
> glibc's functions only.

I'd like Roland's opinion on this.  Roland, for many functions using
dir_lookup we get EINVAL rathern than the ENOENT required by POSIX
when a pathname is the empty string "".  Where should this be fixed?

Thanks,
Marcus