From: Kris Van Hees <kris.van.hees@oracle.com>
To: Bruce McCulloch <bruce.mcculloch@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>, dtrace@lists.linux.dev
Subject: Re: [PATCH] Update llms-txt and add README
Date: Thu, 16 Oct 2025 19:37:39 -0400 [thread overview]
Message-ID: <aPGBw+TC++olxL+j@oracle.com> (raw)
In-Reply-To: <150a690f-7ef5-4695-8508-0661a0aade21@oracle.com>
On Thu, Oct 16, 2025 at 03:51:12PM -0700, Bruce McCulloch wrote:
>
>
> On 10/16/25 3:25 PM, Kris Van Hees wrote:
> > > +## Files
> > > +| File | Description |
> > > +|------|--------------|
> > > +| `llms-dtrace-short.txt` | Compact reference used to bootstrap LLMs for DTrace knowledge. |
> > > +| `llms-dtrace-complete.txt` | Full expanded reference (available from the [DTrace-utils repo](https://github.com/oracle/dtrace-utils/tree/devel/llm)). |
> > > +| `dtrace-llms.html` | Blog-style introduction explaining how to use these context files with LLMs and why DTrace is well-suited for machine-generated tracing. |
> > This file is not included in the patch. I would expect it to be included since
> > it is referenced here.
> Ah yes, I was initially under the impression that this was going in the blog
> git, hence the inclusion ... I will remove the reference.
Thanks
> > > +2. **Load the context file into your LLM session**
> > > +
> > > + - 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 context files are not currently included in the DTrace RPM, so installing
> > DTrace would not make them available. If they are to be included in the RPM,
> > we need to determine where they should be installed and then these instructions
> > should reference that location explicitly.
> Good catch! I'll include a link here.
> Though, to be fair, if users are reading this README, they likely already
> have access to the repo that it covers.
That works for me. I don;t know where we would want to install something like
this anyway, so not installing it at this point is perfectly fine.
prev parent reply other threads:[~2025-10-16 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 20:53 [PATCH] Update llms-txt and add README Bruce McCulloch
2025-10-16 22:25 ` Kris Van Hees
2025-10-16 22:51 ` Bruce McCulloch
2025-10-16 23:37 ` Kris Van Hees [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aPGBw+TC++olxL+j@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=bruce.mcculloch@oracle.com \
--cc=dtrace@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.