9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dusan3sic@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] print() in kernel space doesn't work like I would think
Date: Thu, 31 Aug 2023 12:46:52 -0400	[thread overview]
Message-ID: <16935004120.4cE3.730663@composer.9fans.topicbox.com> (raw)
In-Reply-To: <D9B54C4FE7CE164262847A7C775927A8@eigenstate.org>

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

> try
> 
> cat /dev/kmesg
> or
> cat /dev/kprint

/dev/kmesg outputs the boot output I was talking about, but there wasn't my print.

dev/kprint doesn't print anything and doesn't let me finish the program. I was looking at this <https://9p.io/wiki/plan9/avoiding_screen_pollution_from_kernel_messages/index.html> and did that but no luck there neither. It says null list concatenation when I am booting it and I think it's because $sysname is empty. When I say smth random instead of sysname it makes the file but it's still empty. 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te1d00dae663114b2-Mc46eb4d9cbdcc3a2e9462e3c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1509 bytes --]

  reply	other threads:[~2023-08-31 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 15:43 dusan3sic
2023-08-31 15:48 ` Steve Simon
2023-08-31 16:27 ` ori
2023-08-31 16:31   ` ori
2023-08-31 16:46     ` dusan3sic [this message]
2023-08-31 16:58       ` dusan3sic
2023-08-31 17:25         ` dusan3sic
2023-08-31 17:34           ` ori
2023-09-01 10:59             ` dusan3sic
2023-08-31 19:42           ` ori
2023-08-31 16:53     ` dusan3sic
2023-08-31 17:20       ` ori

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=16935004120.4cE3.730663@composer.9fans.topicbox.com \
    --to=dusan3sic@gmail.com \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).