Joe Kelsey wrote: > > OK, this is a bug. The semantics don't conform to POSIX. > ... > > I rather imagine the correct thing to do is to root it in the FS, > > and, without a leading '/', treat it as relative to the process > > current directory. > > > > Basically, this is not a two line fix... it's a lot of work, to > > get a filesystem object to use. > > I think that it *is* a two-line fix. Remove the maximum length (or > impose a maximum length of MAX_PATHNAMELEN), and simply remove the whole > '/' checking. Then, the private namespace correctly emulates posix > semantics, except for the rooted versus relative stuff, which would be > *really* hard to do in a private namespace and of questionable value anyway.
Sorry, but Garrett was right about the implementation: it should not be using a private namespace in the first place. Making it work for a private namespace that shouldn't be there in the first place seems really questionable, to me... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
