Date: Fri, 27 Apr 2007 11:51:54 -0400 From: John Baldwin <jhb@freebsd.org> To: Marc =?iso-8859-1?q?L=F6rner?= <marc.loerner@hob.de> Cc: freebsd-hackers@freebsd.org Subject: Re: Usage of kern_* functions in kernel Message-ID: <200704271151.54720.jhb@freebsd.org> In-Reply-To: <200704270843.16908.marc.loerner@hob.de> References: <200704261408.19885.marc.loerner@hob.de> <200704261349.35661.jhb@freebsd.org> <200704270843.16908.marc.loerner@hob.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 27 April 2007 02:43:16 am Marc L=F6rner wrote: > On Thursday 26 April 2007 19:49, John Baldwin wrote: > > On Thursday 26 April 2007 08:08:19 am Marc L=F6rner wrote: > > > Hello, > > > I googled but found nothing about the usage of the kern_* functions > > > (kern_open, kern_close, kern_pwritev, kern_preadv) that are located in > > > vfs_syscalls.c > > > > > > When I use kern_open to open a file within the kernel, I get an error. > > > When I use the normal vn_open function instead, all works well. > > > > > > So my question is which functions are recommended by you kernel-hacke= rs > > > for use within kernelspace? > > > > > > And here a second question: Is it possible to open/use the console=20 driver > > > in kernelspace within the functions mentioned above? > > > If not, can you give me some pointers on where I can find this > > > information! > > > > kern_XXX are generally used by system calls such as alternative ABIs, e= tc. >=20 > so, you would recommend using the vn_* functions instead? In general userland should open files rather than the kernel. =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704271151.54720.jhb>