linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Subject: Would an "information module" be useful?
Date: Sun, 22 Sep 2013 19:05:31 +0200	[thread overview]
Message-ID: <l1n80j$ofi$1@ger.gmane.org> (raw)

Hello,

I became interested in an use case where I want to pass customised data from the
boot command-line to other user processes. I have read the available
documentation in the way that kernel modules provide such a means to get
additional parameters recorded.

I have got the understanding that a kernel module provides also a name space for
such boot parameters. (Are they also called "attributes" there?)
Now I would be interested to create a module for my needs so that the passed
data will be stored in the sys file system. Which software component is
responsible for this task?

I find that another implementation detail needs more clarification. The modules
usually drive some hardware.
https://www.kernel.org/doc/Documentation/filesystems/sysfs.txt

But I am looking for a kind of kernel module which does not serve any hardware.
I imagine that it should be sufficient to register it as a simple information sink.

How do you think about my considerations?
Would you like to share any alternative ideas?

Regards,
Markus


             reply	other threads:[~2013-09-22 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22 17:05 Markus Elfring [this message]
2013-09-22 18:23 ` Would an "information module" be useful? richard -rw- weinberger
2013-09-22 19:51   ` Markus Elfring
2013-09-22 19:59     ` Richard Weinberger
2013-09-22 20:30       ` Markus Elfring
2013-09-22 20:37         ` Richard Weinberger
2013-09-23  2:38           ` Markus Elfring
2013-09-23  5:47             ` Richard Weinberger

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='l1n80j$ofi$1@ger.gmane.org' \
    --to=markus.elfring@web.de \
    --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;
as well as URLs for NNTP newsgroup(s).