9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Peter Bosch <pb@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] a strange file in /proc/n/
Date: Mon,  3 Nov 2003 12:17:13 -0500	[thread overview]
Message-ID: <2011109df70ae7131ff7e8c61ca8160c@plan9.bell-labs.com> (raw)
In-Reply-To: <1B3876EF-0E21-11D8-B19A-000393CBA46C@mac.com>

> Today I have noticed that proc(3) device contains a strange-looking
> file.
> (the file name is on the "0000030" line)
>
> term% ls -l|sed 1q|xd -c
> 0000000   -  -  r  -  -  r  w  x  r  w  x     p     0
> 0000010   k  i  w  a  n  e     k  i  w  a  n  e        3
> 0000020   1     N  o  v        3     2  3  :  4  0     '
> 0000030   = \r 1b c2 80  m 01  ' \n
> 0000039
> term%
>
> I glanced at /sys/src/9/port/devproc.c, but couldn't find where it came
> from. What is this?

already fixed - my mistake.  sorry.



      reply	other threads:[~2003-11-03 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 17:13 kiwane
2003-11-03 17:17 ` Peter Bosch [this message]

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=2011109df70ae7131ff7e8c61ca8160c@plan9.bell-labs.com \
    --to=pb@research.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).