[DTrace-devel] [PATCH v2] Remove spurious references to Oracle
eugene.loh at oracle.com
eugene.loh at oracle.com
Tue Mar 10 21:36:39 UTC 2026
From: Eugene Loh <eugene.loh at oracle.com>
Signed-off-by: Eugene Loh <eugene.loh at oracle.com>
---
README | 2 +-
cmd/dtrace.8 | 22 +++++-----
doc/tutorial/1.IntroducingDTrace.md | 4 +-
.../2.TracingOperatingSystemBehavior.md | 44 +++++++++----------
.../3.TracingUserSpaceApplications.md | 16 +++----
dtprobed/dtprobed.8 | 6 +--
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 +-
12 files changed, 60 insertions(+), 60 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/cmd/dtrace.8 b/cmd/dtrace.8
index 1f2d48a07..778d431f4 100644
--- a/cmd/dtrace.8
+++ b/cmd/dtrace.8
@@ -1,9 +1,9 @@
'\" te
.\" Oracle Linux DTrace.
-.\" Copyright (c) 2009, 2024, Oracle and/or its affiliates. All Rights Reserved.
+.\" Copyright (c) 2009, 2026, Oracle and/or its affiliates. All Rights Reserved.
.\" Licensed under the Universal Permissive License v 1.0 as shown at
.\" http://oss.oracle.com/licenses/upl.
-.TH dtrace 8 "22 Oct 2014" "Oracle Linux" "Linux Programmer's Manual"
+.TH DTRACE 8 "Mar 2026" "dtrace" "Linux Programmer's Manual"
.SH NAME
dtrace \- DTrace dynamic tracing compiler and tracing utility
.SH SYNOPSIS
@@ -39,7 +39,7 @@ dtrace \- DTrace dynamic tracing compiler and tracing utility
.LP
DTrace is a comprehensive dynamic tracing framework for the Linux operating system. DTrace provides a powerful infrastructure that permits administrators, developers, and service personnel to concisely answer arbitrary questions about the behavior of the operating system and user programs.
.LP
-The \fIOracle Linux DTrace Guide\fP describes how to use DTrace to observe, debug, and tune system behavior. Refer to this book for a detailed description of DTrace features, including the bundled DTrace observability tools, instrumentation providers, and the D programming language.
+The \fIUsing DTrace for System Tracing\fP describes how to use DTrace to observe, debug, and tune system behavior. Refer to this book for a detailed description of DTrace features, including the bundled DTrace observability tools, instrumentation providers, and the D programming language.
.LP
The \fBdtrace\fP command provides a generic interface to the essential services provided by the DTrace facility, including:
.RS +4
@@ -57,7 +57,7 @@ Options that generate program stability reports
Options that modify DTrace tracing and buffering behavior and enable additional D compiler features
.RE
.LP
-You can use \fBdtrace\fP to create D scripts by using it in a \fB#!\fP declaration to create an interpreter file. You can also use \fBdtrace\fP to attempt to compile D programs and determine their properties without actually enabling tracing using the \fB\-e\fP option. See \fBOPTIONS\fP. See the \fIOracle Linux DTrace Guide\fP for detailed examples of how to use the \fBdtrace\fP utility to perform these tasks.
+You can use \fBdtrace\fP to create D scripts by using it in a \fB#!\fP declaration to create an interpreter file. You can also use \fBdtrace\fP to attempt to compile D programs and determine their properties without actually enabling tracing using the \fB\-e\fP option. See \fBOPTIONS\fP. See the \fIUsing DTrace for System Tracing\fP for detailed examples of how to use the \fBdtrace\fP utility to perform these tasks.
.SH OPTIONS
.LP
The arguments accepted by the \fB\-P\fP, \fB\-m\fP, \fB\-f\fP, \fB\-n\fP, and \fB\-i\fP options can include an optional D language \fIpredicate\fP enclosed in slashes \fB//\fP and optional D language \fIaction\fP statement list enclosed in braces \fB{}\fP. D program code specified on the command line must be appropriately quoted to avoid interpretation of meta-characters by the shell.
@@ -68,7 +68,7 @@ The following options are supported:
Set principal trace buffer size (\fIbufsz\fP). The trace buffer size can include any of the size suffixes \fBk\fP, \fBm\fP, \fBg\fP, or \fBt\fP. If the buffer space cannot be allocated, \fBdtrace\fP attempts to reduce the buffer size or exit depending on the setting of the \fBbufresize\fP property.
.TP
\fB\-c\fP \fIcmd\fP
-Run the specified command \fIcmd\fP and exit upon its completion. If more than one \fB\-c\fP option is present on the command line, \fBdtrace\fP exits when all commands have exited, reporting the exit status for each child process as it terminates. The process-ID of the first command is made available to any D programs specified on the command line or using the \fB\-s\fP option through the \fB$target\fP macro variable. Refer to the \fIOracle Linux DTrace Guide\fP for more information on macro variables.
+Run the specified command \fIcmd\fP and exit upon its completion. If more than one \fB\-c\fP option is present on the command line, \fBdtrace\fP exits when all commands have exited, reporting the exit status for each child process as it terminates. The process-ID of the first command is made available to any D programs specified on the command line or using the \fB\-s\fP option through the \fB$target\fP macro variable. Refer to the \fIUsing DTrace for System Tracing\fP for more information on macro variables.
.TP
\fB\-C\fP
Run the C preprocessor \fBcpp\fP(1) over D programs before compiling them. You can pass options to the C preprocessor using the \fB\-D\fP, \fB\-U\fP, \fB\-I\fP, and \fB\-H\fP options. You can select the degree of C standard conformance if you use the \fB\-X\fP option. For a description of the set of tokens defined by the D compiler when invoking the C preprocessor, see \fB\-X\fP.
@@ -116,7 +116,7 @@ Specify probe name to trace or list (\fB\-l\fP option). The corresponding argume
Specify the \fIoutput\fP file for the \fB\-G\fP, \fB\-h\fP, and \fB\-l\fP options, or for the traced data itself. If the \fB\-G\fP option is present and the \fB\-s\fP option's argument is of the form \fIfilename\fP\fB\&.d\fP and \fB\-o\fP is not present, the default output file is \fIfilename\fP\fB\&.o\fP. Otherwise the default output file is \fBd.out\fP.
.TP
\fB\-p\fP \fIpid\fP
-Grab the specified process-ID \fIpid\fP, cache its symbol tables, and exit upon its completion. If more than one \fB\-p\fP option is present on the command line, \fBdtrace\fP exits when all commands have exited, reporting the exit status for each process as it terminates. The first process-ID is made available to any D programs specified on the command line or using the \fB\-s\fP option through the \fB$target\fP macro variable. Refer to the \fIOracle Linux DTrace Guide\fP for more information on macro variables.
+Grab the specified process-ID \fIpid\fP, cache its symbol tables, and exit upon its completion. If more than one \fB\-p\fP option is present on the command line, \fBdtrace\fP exits when all commands have exited, reporting the exit status for each process as it terminates. The first process-ID is made available to any D programs specified on the command line or using the \fB\-s\fP option through the \fB$target\fP macro variable. Refer to the \fIUsing DTrace for System Tracing\fP for more information on macro variables.
.TP
\fB\-P\fP \fIprovider\fP \fB[[\fP\fIpredicate\fP\fB]\fP \fIaction\fP]
Specify provider name to trace or list (\fB\-l\fP option). The remaining probe description fields module, function, and name are left blank and match any probes regardless of the values in those fields. The \fB\-P\fP argument can be suffixed with an optional D probe clause. You can specify more than one \fB\-P\fP option on the command line at a time.
@@ -134,23 +134,23 @@ Show D compiler intermediate code. The D compiler produces a report of the inter
Undefine the specified \fIname\fP when invoking \fBcpp\fP(1) (enabled using the \fB-C\fP option). This option passes the \fB-U\fP option to each \fBcpp\fP invocation.
.TP
\fB\-v\fP
-Set verbose mode. If the \fB\-v\fP option is specified, \fBdtrace\fP produces a program stability report showing the minimum interface stability and dependency level for the specified D programs. DTrace stability levels are explained in further detail in the \fIOracle Linux DTrace Guide\fP.
+Set verbose mode. If the \fB\-v\fP option is specified, \fBdtrace\fP produces a program stability report showing the minimum interface stability and dependency level for the specified D programs. DTrace stability levels are explained in further detail in the \fIUsing DTrace for System Tracing\fP.
.TP
\fB\-V\fP
-Report the highest D programming interface version supported by \fBdtrace\fP. The version information is printed to \fBstdout\fP and the \fBdtrace\fP command exits. Refer to the \fIOracle Linux DTrace Guide\fP for more information about DTrace versioning features. In conjunction with \fB\-v\fP, also reports information on the version of the \fBdtrace\fP(1) tool and associated library.
+Report the highest D programming interface version supported by \fBdtrace\fP. The version information is printed to \fBstdout\fP and the \fBdtrace\fP command exits. Refer to the \fIUsing DTrace for System Tracing\fP for more information about DTrace versioning features. In conjunction with \fB\-v\fP, also reports information on the version of the \fBdtrace\fP(1) tool and associated library.
.TP
\fB\-w\fP
Permit destructive actions in D programs specified using the \fB\-s\fP, \fB\-P\fP, \fB\-m\fP, \fB\-f\fP, \fB\-n\fP, or \fB\-i\fP options. If the \fB\-w\fP option is not specified, \fBdtrace\fP does not permit the compilation or enabling of a D program that contains destructive actions.
.TP
\fB\-x\fP \fIarg\fP [\fI=val\fP]
-Enable or modify a DTrace runtime option or D compiler option. The list of options is found in the \fIOracle Linux DTrace Guide\fP. Boolean options are enabled by specifying their name. Options with values are set by separating the option name and value with an equals sign (\fB=\fP).
+Enable or modify a DTrace runtime option or D compiler option. The list of options is found in the \fIUsing DTrace for System Tracing\fP. Boolean options are enabled by specifying their name. Options with values are set by separating the option name and value with an equals sign (\fB=\fP).
.TP
\fB\-Z\fP
Permit probe descriptions that match zero probes. If the \fB\-Z\fP option is not specified, \fBdtrace\fP reports an error and exits if any probe descriptions specified in D program files (\fB\-s\fP option) or on the command line (\fB\-P\fP, \fB\-m\fP, \fB\-f\fP, \fB\-n\fP, or \fB\-i\fP options) contain descriptions that do not match any known probes.
.
.SH OPERANDS
.LP
-You can specify zero or more additional arguments on the \fBdtrace\fP command line to define a set of macro variables (\fB$1\fP, \fB$2\fP, and so forth). The additional arguments can be used in D programs specified using the \fB\-s\fP option or on the command line. The use of macro variables is described further in the \fIOracle Linux DTrace Guide\fP.
+You can specify zero or more additional arguments on the \fBdtrace\fP command line to define a set of macro variables (\fB$1\fP, \fB$2\fP, and so forth). The additional arguments can be used in D programs specified using the \fB\-s\fP option or on the command line. The use of macro variables is described further in the \fIUsing DTrace for System Tracing\fP.
.
.SH EXIT STATUS
.LP
@@ -187,7 +187,7 @@ Options set this way are overridden both by options specified via \fB\-x\fP on t
.BR ssh (1),
.BR dtprobed (1)
.LP
-.I Oracle Linux DTrace Guide
+.I Using DTrace for System Tracing
.
.SH USAGE
.LP
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/dtprobed/dtprobed.8 b/dtprobed/dtprobed.8
index 2ebe89ccc..046b2a480 100644
--- a/dtprobed/dtprobed.8
+++ b/dtprobed/dtprobed.8
@@ -1,9 +1,9 @@
'\" te
.\" Oracle Linux DTrace.
-.\" Copyright (c) 2009, 2024, Oracle and/or its affiliates. All Rights Reserved.
+.\" Copyright (c) 2009, 2026, Oracle and/or its affiliates. All Rights Reserved.
.\" Licensed under the Universal Permissive License v 1.0 as shown at
.\" http://oss.oracle.com/licenses/upl.
-.TH dtrace 8 "22 Oct 2023" "Oracle Linux" "Linux Programmer's Manual"
+.TH DTRACE 8 "Mar 2026" "dtrace" "Linux Programmer's Manual"
.SH NAME
dtprobed \- USDT-tracking daemon
.SH SYNOPSIS
@@ -61,4 +61,4 @@ and \fBdtprobed\fP, and can change between releases: on upgrade, \fBdtprobed\fP
.
.BR dtrace (8)
.LP
-.I Oracle Linux DTrace Guide
+.I Using DTrace for System Tracing
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