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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
