From: Andreas Tobler <toa@pop.agri.ch>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: proc_fs Howto for 2.2.X?
Date: Tue, 28 Nov 2000 08:50:36 +0100 [thread overview]
Message-ID: <3A2363C2.BA966C18@pop.agri.ch> (raw)
Hi,
Is there a paper around which describes the use of the proc_fs in the
actual 2.2.17 and up kernels? All I have is the Rubini book which is a
bit aged regarding the proc_fs, and this guide:
http://www.ibiblio.org/mdw/LDP/lkmpg/mpg.html. Also a bit dated.
Exactly what I'm looking for is an explanation whether I should use
proc_register/unregister or create_proc_entry/remove_proc_entry.
I know source is the best teacher, but having a look into 2.2.17 I find
tons of proc_register/unregister references.
To solve my problem I had to use create_proc_entry / remove_proc_entry.
Now I'm not sure if this is the right approach for 2.2.17 and up?
If this was discussed already, sorry, a link to the discussion would be
great.
Thanks for any hint, pointer....
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-28 8:16 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=3A2363C2.BA966C18@pop.agri.ch \
--to=toa@pop.agri.ch \
--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