[DTrace-devel] [PATCH] Remove spurious references to Oracle
Kris Van Hees
kris.van.hees at oracle.com
Tue Mar 10 20:00:12 UTC 2026
On Tue, Mar 10, 2026 at 03:06:31PM -0400, eugene.loh at oracle.com wrote:
> From: Eugene Loh <eugene.loh at oracle.com>
>
> Another file to clean up at some point would be cmd/dtrace.8.
Why not as part of this patch? Seems to make sense to do it all at once.
> Signed-off-by: Eugene Loh <eugene.loh at oracle.com>
> ---
> README | 2 +-
> doc/tutorial/1.IntroducingDTrace.md | 4 +-
> .../2.TracingOperatingSystemBehavior.md | 44 +++++++++----------
> .../3.TracingUserSpaceApplications.md | 16 +++----
> libdtrace/dt_prov_io.c | 2 +-
> libdtrace/dt_prov_profile.c | 2 +-
> llm/README.md | 4 +-
> llm/llms-dtrace-complete.txt | 8 ++--
> llm/llms-dtrace-short.txt | 8 ++--
> test/unittest/options/tst.strip.sh | 2 +-
> 10 files changed, 46 insertions(+), 46 deletions(-)
>
> diff --git a/README b/README
> index c7f704ed7..3dd487695 100644
> --- a/README
> +++ b/README
> @@ -1,4 +1,4 @@
> -Linux DTrace v2.0 for Oracle Unbreakable Enterprise Kernel 6.
> +Linux DTrace v2.0.
> ------------
>
> This is the official Linux port of the advanced tracing tool DTrace.
> diff --git a/doc/tutorial/1.IntroducingDTrace.md b/doc/tutorial/1.IntroducingDTrace.md
> index 3236edf82..dffca17f7 100644
> --- a/doc/tutorial/1.IntroducingDTrace.md
> +++ b/doc/tutorial/1.IntroducingDTrace.md
> @@ -60,7 +60,7 @@ you can choose which method best suits your needs.
>
> DTrace is a comprehensive dynamic tracing facility that was first
> developed for use on the Solaris operating system (now known as
> -Oracle Solaris) and subsequently ported to Oracle Linux.
> +Oracle Solaris) and subsequently ported to Linux.
> You can use
> DTrace to explore the operation of your system to better
> understand how it works, to track down performance problems across
> @@ -126,7 +126,7 @@ For more information about using DTrace, see the
>
> ### About DTrace Providers
>
> -Here are the providers in the Oracle Linux implementation of DTrace:
> +Here are the providers in the Linux implementation of DTrace:
>
> ```
> kernel user space
> diff --git a/doc/tutorial/2.TracingOperatingSystemBehavior.md b/doc/tutorial/2.TracingOperatingSystemBehavior.md
> index b3445ab6d..edfc89c01 100644
> --- a/doc/tutorial/2.TracingOperatingSystemBehavior.md
> +++ b/doc/tutorial/2.TracingOperatingSystemBehavior.md
> @@ -9,8 +9,8 @@ investigate what is happening in the operating system.
> The `proc` probes enable you to trace process creation and termination,
> execution of new program images, and signal processing on a system. See
> [Proc Provider](../userguide/reference/dtrace_providers_proc.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for a description of the `proc` probes and their arguments.
>
> #### Example: Monitoring the System as Programs Are Executed (execcalls.d)
> @@ -122,8 +122,8 @@ to copy arg2 bytes and then add a NUL terminating character after those bytes,
> which are possibly already NUL-terminated.
> See
> [Pointers and Address Spaces](../userguide/reference/dtrace-ref-PointersandScalarArrays.md#pointers_and_address_spaces)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md).
> +in
> +[Using DTrace for System Tracing](../userguide/index.md).
>
> ```
> # dtrace -q -s syscalls.d
> @@ -149,8 +149,8 @@ Use a conversion specifier such as `%-4d`.
>
> See
> [printf](../userguide/reference/function_printf.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for a description of the function.
>
> The process ID and user ID are available as the variables
> @@ -291,8 +291,8 @@ Replace the `trace()` call in
>
> See
> [Profile Provider](../userguide/reference/dtrace_providers_profile.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for a description of the probes.
>
> #### Solution to Exercise and Example: Using tick Probes
> @@ -713,8 +713,8 @@ is determined by examining the `pr_pid` member of the `psinfo_t` data
> structure that is pointed to by the `args[0]` probe argument.
> For more information about the arguments to `proc` probes, see
> [Proc Provider](../userguide/reference/dtrace_providers_proc.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md).
> +in
> +[Using DTrace for System Tracing](../userguide/index.md).
>
> The program uses the value of the child process ID to initialize
> globally unique associative array entries, such as `p_pid[childpid]`.
> @@ -845,8 +845,8 @@ minimum value, standard deviation, and summation of the data being gathered,
> respectively.
> See
> [Aggregations](../userguide/reference/aggregation.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for descriptions of aggregation functions.
>
> DTrace indexes the results of an aggregation by using a tuple
> @@ -1107,8 +1107,8 @@ See
> [`fds`](../userguide/reference/dtrace_builtin_variable_reference.md#dt_ref_var_fds)
> and
> [`fileinfo_t`](../userguide/reference/dtrace_providers_io.md#dt_ref_iofile_prov)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for more information.
>
> The [`trunc()`](../userguide/reference/function_trunc.md) function
> @@ -1133,8 +1133,8 @@ number or `"total"`.
>
> See
> [Sched Provider](../userguide/reference/dtrace_providers_sched.md)
> - in the
> - [Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> + in
> + [Using DTrace for System Tracing](../userguide/index.md)
> for a description of the `sched:::on-cpu`
> probe.
>
> @@ -1226,8 +1226,8 @@ Use the `lquantize()` and `quantize()` functions to display
> linear and power-of-two frequency distributions of data.
> See
> [Aggregations](../userguide/reference/aggregation.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for a description of aggregation functions.
>
> #### Example: Displaying the Distribution of Read Sizes Resulting From a Command
> @@ -1312,15 +1312,15 @@ function is used to display the results of the aggregation.
>
> See
> [IO Provider](../userguide/reference/dtrace_providers_io.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for a description of the arguments to the
> `io:::start` and `io:::done` probes.
>
> See
> [printa](../userguide/reference/function_printa.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md)
> +in
> +[Using DTrace for System Tracing](../userguide/index.md)
> for a description of the function.
>
> After running the program for approximately a minute, type
> diff --git a/doc/tutorial/3.TracingUserSpaceApplications.md b/doc/tutorial/3.TracingUserSpaceApplications.md
> index 1d9bf69f2..1121a583f 100644
> --- a/doc/tutorial/3.TracingUserSpaceApplications.md
> +++ b/doc/tutorial/3.TracingUserSpaceApplications.md
> @@ -293,21 +293,21 @@ For more information on how to use the `pid` provider to trace
> user function entry and return or on specific instruction offsets,
> see
> [Pid Provider](../userguide/reference/dtrace_providers_pid.md)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md).
> +in
> +[Using DTrace for System Tracing](../userguide/index.md).
>
> ### Adding USDT Probes to an Application
>
> In this section, we practice adding USDT probes to an application.
> For background information and other details, see
> [Adding USDT Probes to Application Code](../userguide/reference/dtrace-ref-StaticallyDefinedTracingofUserApplications.md#dt_ref_usdt_probe_add_prov)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md).
> +in
> +[Using DTrace for System Tracing](../userguide/index.md).
>
> To get started, you will need to create a `.d` file, as described in
> [Defining USDT Providers and Probes](../userguide/reference/dtrace-ref-StaticallyDefinedTracingofUserApplications.md#dt_ref_usdtprobes_prov)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md).
> +in
> +[Using DTrace for System Tracing](../userguide/index.md).
>
> >Note:
> >
> @@ -431,8 +431,8 @@ and a false value if the associated probe is not enabled.
> Next, you will need to modify the `makefile` file.
> For step-by-step instructions, See
> [Building Applications With USDT Probes](../userguide/reference/dtrace-ref-StaticallyDefinedTracingofUserApplications.md#dt_ref_usdt_build_prov)
> -in the
> -[Oracle Linux: DTrace Reference Guide](../userguide/index.md).
> +in
> +[Using DTrace for System Tracing](../userguide/index.md).
>
> #### Exercise: Directing makefile to Re-Create the dprime.h File
>
> diff --git a/libdtrace/dt_prov_io.c b/libdtrace/dt_prov_io.c
> index db768bb72..7e2238564 100644
> --- a/libdtrace/dt_prov_io.c
> +++ b/libdtrace/dt_prov_io.c
> @@ -591,7 +591,7 @@ static int trampoline(dt_pcb_t *pcb, uint_t exitlbl)
> done:
> /*
> * Note: DTrace does not currently support the use of fileinfo_t with
> - * io probes. In Oracle Linux, there is no information about the file
> + * io probes. In Linux, there is no information about the file
> * where the I/O request originated at the point where the io probes
> * fire.
> */
> diff --git a/libdtrace/dt_prov_profile.c b/libdtrace/dt_prov_profile.c
> index 60da094a2..de7e02120 100644
> --- a/libdtrace/dt_prov_profile.c
> +++ b/libdtrace/dt_prov_profile.c
> @@ -224,7 +224,7 @@ static int trampoline(dt_pcb_t *pcb, uint_t exitlbl)
> * TODO: For profile-n probes:
> * dctx->mst->argv[2] = elapsed nsecs
> * The documentation does not say elapsed since when?
> - * From the legacy port to Oracle Linux, in dtrace/profile_dev.c,
> + * From the legacy port to Linux, in dtrace/profile_dev.c,
> * in profile_prof_fn(), it appears that we have a per-CPU variable
> * that tracks the expected time of the next profile probe.
> * Each time the probe fires, we compute arg2 = time - expected
> diff --git a/llm/README.md b/llm/README.md
> index 2992bf7bc..117783f92 100644
> --- a/llm/README.md
> +++ b/llm/README.md
> @@ -2,7 +2,7 @@
>
> ## Overview
> These files provide structured **context packs** (`llms-txt` format) for use with large language models (LLMs) such as GPT-4 or Claude.
> -They teach the model how to write **correct, safe, and complete DTrace programs** for Oracle Linux.
> +They teach the model how to write **correct, safe, and complete DTrace programs** for Linux.
>
> The goal is to let engineers and administrators generate working D scripts in natural language ??? without having to memorize the entire D language syntax.
>
> @@ -39,7 +39,7 @@ The goal is to let engineers and administrators generate working D scripts in na
>
> - In ChatGPT, Claude, or another interface that supports file context, click the ???+??? icon and upload `llms-dtrace-short.txt`.
>
> - - The model will automatically ingest the reference and understand how to write runnable DTrace programs for Oracle Linux.
> + - The model will automatically ingest the reference and understand how to write runnable DTrace programs for Linux.
>
> 3. **Start asking questions in natural language**
>
> diff --git a/llm/llms-dtrace-complete.txt b/llm/llms-dtrace-complete.txt
> index 818e0086f..07275cb9d 100644
> --- a/llm/llms-dtrace-complete.txt
> +++ b/llm/llms-dtrace-complete.txt
> @@ -1,4 +1,4 @@
> -You are a senior systems engineer with deep expertise in writing DTrace programs for Oracle Linux. You understand that DTrace is one of the most powerful tools for diagnosing complex system behavior, and you will always provide complete, correct scripts that compile and run cleanly. Every answer must include the full text of a runnable D program, with appropriate shebangs, predicates, and comments where helpful.
> +You are a senior systems engineer with deep expertise in writing DTrace programs for Linux. You understand that DTrace is one of the most powerful tools for diagnosing complex system behavior, and you will always provide complete, correct scripts that compile and run cleanly. Every answer must include the full text of a runnable D program, with appropriate shebangs, predicates, and comments where helpful.
>
> You favor stable providers (such as syscall, proc, sched, profile, io, usdt, pid) and safe idioms that avoid invalid memory access or unnecessary output. You use predicates to filter load, aggregations instead of unbounded per-event prints, and you always include an ERROR clause when relevant. Your answers are precise, professional, and free of placeholders or half-solutions.
>
> @@ -7,15 +7,15 @@ DO NOT RECOMMEND DANGEROUS OPERATIONS UNLESS THERE IS AN ALTERNATIVE. Do not rec
> WARNING: Forbidden constructs: if, else, for, while, switch, etc.
> For example, instead of using `if`, use predicates and ternary operators only.
>
> -Below you will find all the information you need to reference in order to create correct and reliable DTrace programs for Oracle Linux.
> +Below you will find all the information you need to reference in order to create correct and reliable DTrace programs for Linux.
>
> -After consuming this information, inform the user that you are ready to begin writing DTrace scripts for Oracle Linux.
> +After consuming this information, inform the user that you are ready to begin writing DTrace scripts for Linux.
>
> DTRACE (ORACLE LINUX) ??? LLMS.TXT FORMAT
> PART 1: PROGRAM STRUCTURE, PROBE DESCRIPTIONS, PREDICATES, STATEMENTS
>
> ## GOAL
> -Provide a compact, machine-optimized reference so an LLM can generate correct DTrace D programs for Oracle Linux.
> +Provide a compact, machine-optimized reference so an LLM can generate correct DTrace D programs for Linux.
>
> ## PROGRAM STRUCTURE
> A D program is a set of probe clauses; each clause may include an optional predicate and a statement block.
> diff --git a/llm/llms-dtrace-short.txt b/llm/llms-dtrace-short.txt
> index 19d5f73e5..7430f4ba5 100644
> --- a/llm/llms-dtrace-short.txt
> +++ b/llm/llms-dtrace-short.txt
> @@ -1,4 +1,4 @@
> -You are a senior systems engineer with deep expertise in writing DTrace programs for Oracle Linux. You understand that DTrace is one of the most powerful tools for diagnosing complex system behavior, and you will always provide complete, correct scripts that compile and run cleanly. Every answer must include the full text of a runnable D program, with appropriate shebangs, predicates, and comments where helpful.
> +You are a senior systems engineer with deep expertise in writing DTrace programs for Linux. You understand that DTrace is one of the most powerful tools for diagnosing complex system behavior, and you will always provide complete, correct scripts that compile and run cleanly. Every answer must include the full text of a runnable D program, with appropriate shebangs, predicates, and comments where helpful.
>
> You favor stable providers (such as syscall, proc, sched, profile, io, usdt, pid) and safe idioms that avoid invalid memory access or unnecessary output. You use predicates to filter load, aggregations instead of unbounded per-event prints, and you always include an ERROR clause when relevant. Your answers are precise, professional, and free of placeholders or half-solutions.
>
> @@ -7,15 +7,15 @@ DO NOT RECOMMEND DANGEROUS OPERATIONS UNLESS THERE IS AN ALTERNATIVE. Do not rec
> WARNING: Forbidden constructs: if, else, for, while, switch, etc.
> For example, instead of using `if`, use predicates and ternary operators only.
>
> -Below you will find all the information you need to reference in order to create correct and reliable DTrace programs for Oracle Linux.
> +Below you will find all the information you need to reference in order to create correct and reliable DTrace programs for Linux.
>
> -After consuming this information, inform the user that you are ready to begin writing DTrace scripts for Oracle Linux.
> +After consuming this information, inform the user that you are ready to begin writing DTrace scripts for Linux.
>
> DTRACE (ORACLE LINUX) ??? LLMS.TXT FORMAT
> PART 1: PROGRAM STRUCTURE, PROBE DESCRIPTIONS, PREDICATES, STATEMENTS
>
> ## GOAL
> -Provide a compact, machine-optimized reference so an LLM can generate correct DTrace D programs for Oracle Linux.
> +Provide a compact, machine-optimized reference so an LLM can generate correct DTrace D programs for Linux.
>
> ## PROGRAM STRUCTURE
> A D program is a set of probe clauses; each clause may include an optional predicate and a statement block.
> diff --git a/test/unittest/options/tst.strip.sh b/test/unittest/options/tst.strip.sh
> index d25f76af3..a6762cfb9 100755
> --- a/test/unittest/options/tst.strip.sh
> +++ b/test/unittest/options/tst.strip.sh
> @@ -64,7 +64,7 @@ fi
> $objdump >& out.default.txt
>
> # Check results. One can imagine a more stringent check -- like
> -# seeing if the string "Oracle D 2.0" appears in the default case
> +# seeing if particular strings appear in the default case
> # but not in the stripped case -- but here we settle for the stripped
> # case simply being smaller than the default case.
>
> --
> 2.47.3
>
More information about the DTrace-devel
mailing list