From ced11fe2e78a4c5f346555e24684ddd3d46b06ee Mon Sep 17 00:00:00 2001 From: Dru Lavigne Date: Mon, 7 Apr 2014 15:12:06 +0000 Subject: [PATCH] Editorial review of Implementation Differences in DTrace. Need to collaborate with someone who knows more about DTrace to finish the review of the rest of this chapter. Sponsored by: iXsystems --- .../books/handbook/dtrace/chapter.xml | 48 +++++++++---------- 1 file changed, 23 insertions(+), 25 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml b/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml index a4ff233717..a6e6f47813 100644 --- a/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml @@ -103,52 +103,50 @@ that might make this chapter too large. Implementation Differences - While the &dtrace; in &os; is very similar to that found - in &solaris;, differences exist that should be explained before - continuing. The primary difference users will notice is that - on &os;, &dtrace; needs to be specifically enabled. There are - kernel options and modules which must be enabled for &dtrace; to - work properly. These will be explained later. + While the &dtrace; in &os; is similar to that found + in &solaris;, differences do exist. + The primary difference is that + on &os;, &dtrace; needs to be specifically enabled by loading + kernel modules or by compiling a custom kernel with specific + options. - There is a DDB_CTF kernel option which - is used to enable support for loading the CTF + &os; uses the DDB_CTF kernel option + to enable support for loading CTF data from kernel modules and the kernel itself. CTF is the &solaris; Compact C Type Format which encapsulates a reduced form of debugging information similar to DWARF and the venerable stabs. - This CTF data is added to the binaries by the + CTF data is added to binaries by the ctfconvert and ctfmerge build tools. The ctfconvert utility parses DWARF ELF debug sections created by the compiler and ctfmerge merges CTF ELF sections from - objects into either executables or shared libraries. More on - how to enable this for the kernel and &os; build is - forthcoming. + objects into either executables or shared libraries. Some different providers exist for &os; than for &solaris;. Most notable is the dtmalloc provider, which allows tracing malloc() by type in the &os; kernel. - Only root may use &dtrace; on &os;. - This is related to security differences, &solaris; has a few + Due to security differences, only root may use &dtrace; on &os;. + &solaris; has a few low level security checks which do not yet exist in &os;. As such, the /dev/dtrace/dtrace is - strictly limited to root users only. + strictly limited to root. - Finally, the &dtrace; software falls under &sun;'s - CDDL license. The Common - Development and Distribution License comes with &os;, - see the + &dtrace; falls under &sun;'s Common + Development and Distribution License + (CDDL) license. To view this license on &os;, + see /usr/src/cddl/contrib/opensolaris/OPENSOLARIS.LICENSE or view it online at - http://www.opensolaris.org/os/licensing. - - This license means that a &os; kernel with the &dtrace; - options is still BSD licensed; however - the CDDL kicks in when the modules are - distributed in binary form, or the binaries are loaded. + http://www.opensolaris.org/os/licensing. + While a &os; kernel with &dtrace; support + is BSD licensed, + the CDDL is used when the modules are + distributed in binary form or the binaries are loaded.