From owner-freebsd-hackers Sat Nov 11 7:25:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-070.ricochet.net [204.179.136.70]) by hub.freebsd.org (Postfix) with ESMTP id 1BA8E37B479 for ; Sat, 11 Nov 2000 07:25:46 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id HAA02970; Sat, 11 Nov 2000 07:26:15 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011111526.HAA02970@spammie.svbug.com> Date: Sat, 11 Nov 2000 07:26:14 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: printf() To: tlambert@primenet.com Cc: duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011101857.LAA24569@usr08.primenet.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Nov, Terry Lambert wrote: >> A simple question: >> >> Does the kernel function printf() flushes the output immediately, or it is >> possible some data is buffered somewhere and gets lost without printing >> to the console? like the corresponding funtion in the c library. > > There is no buffering comparable to that of the stdio package; > in other words, there is no such thing as an fflush() or setbuf() > call. > >>...[Trimmed]... > > Hope this helps, and hope anyone who has any corrections to this > wil provide them, since this type of documentation needs to be > collected somewhere, and the mailing list archives seem to be the > most appropriate place. > Yes, Thanks Terry. Your explaination is much clearer than mine and it certainly covers the material in a much more concise manner than I know I could in a single writing. > Maybe we can set up an arch-doc list, which we can cross-post > these responses to via Bcc:, without incurring the wrath of the > mailing list manager? An archive of such things (my contributions > in this area are minor, trust me) would be a good thing; PHK > posted a nice internals description the other day that I would > not mind having archived for eternity, without it taking up space > in my email archive. > I agree. Additionally, such a idea could be extended with some simple scripts, if the write wrote a few key phrases at the head of such a message. For instance in this case: Scope: kernel internals Lifetime: Eternal Overrides: None However, that might just be wishful thinking on my part. :-) Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message