docs: remove redundant references to official documentation in multiple tutorial README files

This commit is contained in:
yunwei37
2025-10-01 16:56:59 -07:00
parent 71c89cbcd2
commit 445722e8a3
11 changed files with 6 additions and 16 deletions

View File

@@ -143,7 +143,7 @@ $ sudo cat /sys/kernel/debug/tracing/trace_pipe
## Summary
In this article's example, we learned how to use eBPF's kprobe and kretprobe to capture the unlink system call. For more examples and detailed development guides, please refer to the official documentation of eunomia-bpf: <https://github.com/eunomia-bpf/eunomia-bpf>
In this article's example, we learned how to use eBPF's kprobe and kretprobe to capture the unlink system call.
This article is the second part of the introductory eBPF development tutorial. The next article will explain how to use fentry to monitor and capture the unlink system call in eBPF.

View File

@@ -142,7 +142,7 @@ $ sudo cat /sys/kernel/debug/tracing/trace_pipe
## 总结
通过本文的示例,我们学习了如何使用 eBPF 的 kprobe 和 kretprobe 捕获 unlink 系统调用。更多的例子和详细的开发指南,请参考 eunomia-bpf 的官方文档:<https://github.com/eunomia-bpf/eunomia-bpf>
通过本文的示例,我们学习了如何使用 eBPF 的 kprobe 和 kretprobe 捕获 unlink 系统调用。
本文是 eBPF 入门开发实践教程的第二篇。下一篇文章将介绍如何在 eBPF 中使用 fentry 监测捕获 unlink 系统调用。