From owner-freebsd-doc Tue Dec 17 12: 0:10 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAC4A37B404; Tue, 17 Dec 2002 12:00:09 -0800 (PST) Received: from smtpout.mac.com (A17-250-248-89.apple.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267CC43ED1; Tue, 17 Dec 2002 12:00:09 -0800 (PST) (envelope-from leimy2k@mac.com) Received: from woappsx14.mac.com (woappsx14-en1 [10.13.10.114]) by smtpout.mac.com (8.12.2/MantshX 2.0) with ESMTP id gBHK03xn003456; Tue, 17 Dec 2002 12:00:08 -0800 (PST) Received: from woappsx14 (localhost [127.0.0.1]) by woappsx14.mac.com (8.10.2/8.10.2) with ESMTP id gBHK03D10634; Tue, 17 Dec 2002 12:00:03 -0800 (PST) Message-ID: <2802274.1040155203303.JavaMail.leimy2k@mac.com> Date: Tue, 17 Dec 2002 12:00:03 -0800 (PST) From: David Leimbach To: hiten@uk.FreeBSD.org Subject: RE: Error in example for Kernel module.... Cc: John Baldwin , freebsd-doc@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tuesday, Dec 17, 2002, at 01:02PM, Hiten Pandya wrote: >--- John Baldwin wrote: >> > This is probably minor... >> >> You can use printf in the kernel directly. > >I think he was trying to say, that there are only two occurences of >printf(), i.e. 'Echo device loaded/unloaded', so might as well convert >them to uprintf() for consistency -- or the other way round. I like >that former, but I dont have authority. :) Sorry for my terseness. I am sure that caused confusion. The consistency is part of the comment. The other part has to do with the fact that uprintf displays information on the console. Since these are debugging messages for newbie kernel hackers like myself it seemed appropriate to give the user immediate feedback. Either that or use printf and redirect the user to the system logs which is where I think that output ends up. I made an earlier comment about these not being quite FBSD 5.0 compliant with the function protoypes for read/write since we now have thread *'s instead of proc *'s. Overall I am very impressed with the quality of the documentation the FreeBSD project has compared to other open sourced efforts. I am just trying to help :). Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message