Subject: Re: an in-kernel getcwd() implementation
To: Bill Sommerfeld <firstname.lastname@example.org>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
Date: 03/07/1999 12:31:31
In message <199903071551.PAA07378@orchard.arlington.ma.us>,
Bill Sommerfeld writes:
>> 1) how does it interact with amd's userspace finagling
>> of mount-points?
>Could you be more specific? I haven't used amd for a long time... What
>behavior are you looking for? Does it generate carefully selected
>device/inode numbers or something screwy like that to spoof getcwd?
I havent used it in years, either. I recall amd changing its own idea
of the mount-point without (necessarily) telling the kernel. maybe
I'm misremembering. We can discuss it offline (after i get more
>There isn't a per-process name->vnode cache in NetBSD (or least, not
>one I could find..) so, no, I don't think the additional complexity
systat vmstat keeps printing lines about a namei proc-cache...
now you mention it maybe it never has nonzero hit rate.
nullfs doesnt blow up on mount anymore, but it may still be horribly
broken internally. i just wondered why it was absent.
the rest youve covered. (well, you did ask for it:)