On Fri, Apr 18, 2008 at 11:44:50PM -0700, Tim Rightnour wrote: > > On 18-Apr-2008 Izumi Tsutsui wrote: > > "intended to be used to print autoconfiguration messages" isn't enough? > > It also says aprint_error(9) is prepared "to report the number of errors > > that occurred during a quiet or silent initialization phase." > > > > Anyway, I think actual error accounting should be done by APIs > > like evcnt(9) rather than current aprint(9) family. > > My understanding of the aprint_* API is that aprint is for autoconf only (thus > the a) and log(9) should be used for normal operation. I don't think treating autoconfiguration-related message differently makes sense anymore. For instance, the bit about reporting the number of errors really is outdated in our days: autoconf can happen all the time, not just when the system is cold. Besides, it's not clear what can happen during autoconf. Some pieces of code such as interrupt handlers (or a subsequent worker thread) can report errors during autoconf as well as during normal operation. log(9) doesn't print to the console, that's what makes aprint(9) a convenient API. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "See the look on my face from staying too long in one place [...] every time the morning breaks I know I'm closer to falling" KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
Attachment:
pgpucQOxGVoBZ.pgp
Description: PGP signature