Documenting "porting old to new" examples
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 189
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
There's a bunch of one-liners and small scripts on the internet which almost work with DTrace 2.0 but need a little bit of porting.
@kvanhees has answered my questions on a bunch of them and I've tried to document common issues so far at https://wiki.gentoo.org/wiki/DTrace#Online_examples_not_working. One of them was https://github.com/oracle/dtrace-utils/issues/79#issuecomment-2296561131.
So far, we have:
execveat_commonwhich should be replaced with the more generic entrypointproc:::execopenbeing vulnerable to libc implementation details
We should document other known cases which are known (but not to me) and list the new, idiomatic way of doing the $THING.
(Or maybe it really is just those I listed on the Gentoo wiki and I'm extrapolating too far?)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Gentoo wiki section and the linked oracle/dtrace-utils issue comment, then compare the listed execveat_common and open cases with the current DTrace 2.0 examples. Done means documenting additional known porting problems and the idiomatic replacement for each, or confirming that the existing cases are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, observability-sre
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100