On Sun, Jan 02, 2011 at 10:48:03AM +, David Laight wrote:
> On Sun, Jan 02, 2011 at 09:17:11AM +, David Holland wrote:
> > Because we have at least one FS that may not want paths being looked
> > up to be split on '/', namely rump etfs, and arguably the most
> > important simplification
On Sun, Jan 02, 2011 at 09:17:11AM +, David Holland wrote:
> Because we have at least one FS that may not want paths being looked
> up to be split on '/', namely rump etfs, and arguably the most
> important simplification to VOP_LOOKUP is to make it handle one path
> component at a time, we nee
digest at once.
After thinking about this for a while I think the best approach is to
add a parsepath op, which given a pathname returns the length of the
string to consume.
There are two major questions about how this should work: one is
whether it should be a vnode or fs operation, and the ot
