Sync description of lookup() a bit more to reality.

ok thib@

1 files changed, 7 insertions, 6 deletions

diff --git a/sys/kern/vfs_lookup.c b/sys/kern/vfs_lookup.c
index 8a7b3ff3ea0..09c59058d34 100644
--- a/sys/kern/vfs_lookup.c
+++ b/sys/kern/vfs_lookup.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: vfs_lookup.c,v 1.36 2007/08/07 07:41:59 thib Exp $	*/
+/*	$OpenBSD: vfs_lookup.c,v 1.37 2007/09/08 01:45:58 hshoexer Exp $	*/
 /*	$NetBSD: vfs_lookup.c,v 1.17 1996/02/09 19:00:59 christos Exp $	*/
 
 /*
@@ -253,11 +253,12 @@ badlink:
  * Search a pathname.
  * This is a very central and rather complicated routine.
  *
- * The pathname is pointed to by ni_ptr and is of length ni_pathlen.
- * The starting directory is taken from ni_startdir. The pathname is
- * descended until done, or a symbolic link is encountered. The variable
- * ni_more is clear if the path is completed; it is set to one if a
- * symbolic link needing interpretation is encountered.
+ * The pathname is pointed to by ni_cnd.cn_nameptr and is of length
+ * ni_pathlen.  The starting directory is taken from ni_startdir. The
+ * pathname is descended until done, or a symbolic link is encountered.
+ * If the path is completed the flag ISLASTCN is set in ni_cnd.cn_flags.
+ * If a symbolic link need interpretation is encountered, the flag ISSYMLINK
+ * is set in ni_cnd.cn_flags.
  *
  * The flag argument is LOOKUP, CREATE, RENAME, or DELETE depending on
  * whether the name is to be looked up, created, renamed, or deleted.