public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Colbus <ecolbus@manux.info>
To: linux-kernel@vger.kernel.org
Subject: [RFC][11/11][MANUX] Suggestion : /proc files
Date: Tue, 15 Apr 2014 15:43:18 +0200	[thread overview]
Message-ID: <534D3776.5040907@manux.info> (raw)

Now, a second suggestion : in /proc, besides the pids and the /proc/self
symlink, there are several files that have a length of 0 (according to
stat(2)), but actually have a non-empty content. What about making these
files character-mode device files? I mean, a file whose content is
virtual an whose size is unknown at stat(2)-time, this seems to
correspond more closely to character-mode files that to regular ones.

That's just an idea that came to me, I've not tried it myself, and
perhaps there are compatibility considerations that prevent such a
modification. But even if there is this problem, this doesn't precludes
making any future file in this way. What do you think about it?

Anyways, that was it. Thanks for your attention, and happy hacking!

Emmanuel

                 reply	other threads:[~2014-04-15 14:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=534D3776.5040907@manux.info \
    --to=ecolbus@manux.info \
    --cc=linux-kernel@vger.kernel.org \
    /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