J
Jade
jade.fyi · Personal blog · on HN since 2021
Jade writes technical posts on Nix, NixOS, dotfiles, build systems, and debugging tools such as DTrace on macOS.
What HN saysHN links it for practical Nix guides, including using flakes without flakes, and for a DTrace post. The one comment given is a DTrace question.
15HN people shared it
1linked it in comments
16stories submitted
96story points
5 months agolast shared
2021people per year2026
Most-shared posts
- 1You don't have to use Nix to manage your dotfiles4 people · 7 points · first shared 2025 · 1 comments on HN
- 2Misadventures in DTrace: how to debug the macOS kernel4 people · 6 points · first shared 2025 · discussion on HN
- 3Flakes aren't real and cannot hurt you: using Nix flakes the non-flake way2 people · 73 points · first shared 2024 · 81 comments on HN
- 4The Postmodern Build System2 people · 4 points · first shared 2024 · discussion on HN
- 5Clipper: TLS-transparent HTTP debugging for native apps2 people · 2 points · first shared 2023 · discussion on HN
- 6Docs Tricks and GNUs1 people · 2 points · first shared 2021 · discussion on HN
- 7Pinning NixOS with npins, or how to kill channels forever without flakes1 people · 1 points · first shared 2024 · discussion on HN
- 8Stopping Evaluation from Blocking in Nix1 people · 1 points · first shared 2023 · discussion on HN
What HN people wrote when they linked it
westurner · 2025-11-03
Np. Distributed tracing tools for containers already do this but none have a --diff feature for logging what changed in changed files.
Does this command also track renames?
sudo dtrace -n 'vfs::*:entry { printf("%-16s %-6d %s", execname, pid, probefunc); }' Isn't it just a list of syscalls instead of vfs:*?
Actually, re: Dtrace on MacOS with SIP and apparently without sufficient symbols installed to trace kernel syscalls these days: https://news.ycombinator.com/item?id=38909715
It looks like there's a utility called dtruss which wraps Dtrace on OSX: https://www.google.com/search?q=dtruss
"Misadventures in DTrace: how to debug the macOS kernel" (2025) https://jade.fyi/blog/misadventures-in-dtrace/ :
> My advice, and what I actually did, is to put macOS in a UTM.app VM with nothing of value in it, disable SIP in the VM, and do all further testing in there.
> Once inside a VM with SIP disabled (or with dtrace enabled as a fine-grained policy), DTrace works. dtruss gives some output like the following:
FWIU it is possible to trace Linux containers on Mac OS with e.g. cilium, only if the Linux containers are hosted in a Linux VM.