Subject: re: PF_KEY socket buffer size issue
To: Bill Studenmund <wrstuden@netbsd.org>
From: matthew green <mrg@eterna.com.au>
List: source-changes
Date: 09/11/2003 13:25:29
   On Thu, 11 Sep 2003, matthew green wrote:
   
   >
   >    >>    	routing scket operation case was fixed by using sysctl(NET_RT_DUMP).
   >    > why can't PF_KEY use a sysctl then?
   >
   >    	that's one of the possibility, yes.  i might do that.
   >
   > please do.  a solution that works in all cases without requring
   > /kern to be mounted is highly desirable.
   
   But sysctl is grosser than /kern. They both are hierarchical ways of
   getting info out of the kernel. Everywhere else in the kernel, we
   call that a file system. So why not just expose it as such?
   
   sysctl also has two naming schemes (the text one users are used to and the
   numeric one used internally). Way gross. :-)


perhaps.  the point is that sysctl *is* a part of netbsd that isn't optional.


.mrg.