Skip to content

Conversation

jserv
Copy link
Contributor

@jserv jserv commented Aug 6, 2025

This commit resolves confusion where users expected module output to appear directly in terminal. It also updates documentation to clearly explain that:

  • Module output goes to kernel log ring buffer, not console
  • Use 'dmesg' to view module messages
  • Terminal environment doesn't affect where output goes
  • Provides concrete examples in hello world section

Close #171

Summary by Bito

This pull request enhances the documentation for kernel module output, clarifying that messages are directed to the kernel log ring buffer rather than the terminal. It provides clear instructions for using the 'dmesg' command to view these messages and includes concrete examples in the hello world section to reduce user confusion.

This commit resolves confusion where users expected module output to
appear directly in terminal. It also updates documentation to clearly
explain that:
- Module output goes to kernel log ring buffer, not console
- Use 'dmesg' to view module messages
- Terminal environment doesn't affect where output goes
- Provides concrete examples in hello world section

Close #171
@jserv jserv merged commit 8727425 into master Aug 6, 2025
1 check passed
@jserv jserv deleted the clarify-terminal branch August 6, 2025 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unclear note about term emulator vs virtual console, and journalctl and dmesg

1 participant