Date: Tue, 27 Jan 1998 13:31:54 -0600 (CST) From: Joel Ray Holveck <joelh@gnu.org> To: dyson@FreeBSD.ORG Cc: mike@smith.net.au, doconnor@cain.gsoft.com.au, mike@smith.net.au, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG Subject: Re: File I/O in kernel land (was: Re: 2nd warning: 2.2.6 BETA begins in 10 days!) Message-ID: <199801271931.NAA06176@detlev.UUCP> In-Reply-To: <199801270720.CAA00625@dyson.iquest.net> References: <199801270720.CAA00625@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> As Julian said, see how the code in the kernel handles reading executable >> images. It's moderately painful, but definitely the Right Way to do it. > You should refer to the code in -current, because the older stuff had some > problems. Also, you can do vn_open, vn_read, vn_write, > vn_close if you want to. There are the options to do I/O to/from system > space. The only reason (that I know of) that the exec code doesn't use > the vn_* calls is for efficiency reasons, so lots of stuff is bypassed > and done slightly VMish as opposed to file I/Oish. Gotcha. I'll go over that. > I don't have lots of time to tutor, but what you should be able to do is: I don't ask for tutoring, but being new to the FreeBSD kernel (not to mention relatively new to FreeBSD in general), I do need people to occasionally point me towards functions I can look into. > I know that it seems to be complicated, but not really worse than doing > I/O in user-land on VMS :-). That's actually considerably less complicated than I was anticipating. -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801271931.NAA06176>