From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sat, 26 Mar 2005 12:45:40 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Kernel interface manpages In-Reply-To: <20050326083629.GH93332@smp500.sitetronics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <26029ec71211f29300ddd8b5225f1e38@coraid.com> <20050325183606.GA93332@smp500.sitetronics.com> <20050325200401.GB93332@smp500.sitetronics.com> <20050325202349.GD93332@smp500.sitetronics.com> <20050326083044.GG93332@smp500.sitetronics.com> <20050326083629.GH93332@smp500.sitetronics.com> Topicbox-Message-UUID: 2c377f3a-ead0-11e9-9d60-3106f5b1d025 that would be great. starting with the inferno man pages is probably a good idea, modulo licensing issues which i'm sure can be worked out. on the list of things worth documenting: qio, sleep/wakeup, waserror, spl*, ilock/iunlock, generic driver interfaces: ether, uart, sd, vga. the vita pages cover some of these already. russ On Sat, 26 Mar 2005 09:36:29 +0100, Devon H. O'Dell wrote: > Ok, so spawning from my recent questions from the list, it > appears that we'd probably benefit from some concise, well > written man pages for kernel interfaces. I know Inferno has > (some of?) these, but as with addclock0link, ours does differ. > > I'd be willing to write some extra man pages for kernel > interfaces. What'd be the best way to go about doing this? > Simply read through the {port}fns.h and write? > > Should I do this? > > --Devon > > >