Date: Mon, 5 May 2003 08:54:58 +0200 From: John Hay <jhay@icomtek.csir.co.za> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: cvs-all@FreeBSD.org Subject: Re: Deliberately breaking software (was: cvs commit: src/sys/dev/vinum vinumioctl.c) Message-ID: <20030505065458.GA24741@zibbi.icomtek.csir.co.za> In-Reply-To: <36667.1052116481@critter.freebsd.dk> References: <20030505055618.GA84427@wantadilla.lemis.com> <36667.1052116481@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
May I hijack this a little? > Right now, you still do not use disk_create() to create proper > disk-device in vinum, and that means that features which work with > other disk devices in the system do not work with vinum. ##### beast:~ > man disk_create No manual entry for disk_create ##### This has been bothering me a bit lately. We seem to add new APIs for the kernel, that device drivers etc. should use, but by not documenting them. How should one know which to use and which are not to be used? Think of all the bus_* and other functions too. I think we make life unnecessarily difficult for other device driver writers / mainatiners. Remember there are third party drivers too. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030505065458.GA24741>