From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <1257590719.28012.1344036163@webmail.messagingengine.com>
From: "Ethan Grammatikidis" <eekee57@fastmail.fm>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
References: <55c52a87f0b8c0ac12a81a150f110b2b@brasstown.quanstro.net>
	<20091101184418.GM19125@gradx.cs.jhu.edu>
	<d1c554290911030730m64a7d415k23e5622510438b4f@mail.gmail.com>
In-Reply-To: <d1c554290911030730m64a7d415k23e5622510438b4f@mail.gmail.com>
Date: Sat,  7 Nov 2009 10:45:19 +0000
Subject: Re: [9fans] dtrace for plan 9
Topicbox-Message-UUID: 97d876ae-ead5-11e9-9d60-3106f5b1d025

A comment in MacFUSE changelog got me thinking. Here's the comment:

For example, look at the updated LoopbackFS example file system: the
logging code from it has been removed because better tracing information
can be had using DTrace. Consequently, the file system code is shorter
and easier to read.

I don't know anything specific about DTrace, but I'm thinking a clear,
consistent interface for logging and tracing kernel operations sounds
like a good thing.