From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Srinivasan Venkatraman <srini@dcs.uky.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question on accessing /proc
Date: Mon, 09 Apr 2001 15:51:48 -0400 [thread overview]
Message-ID: <3AD212D4.55E5E8DB@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104091537190.18228-100000@bart.dcs.uky.edu>
Srinivasan Venkatraman wrote:
> I am new to this list. I did go through the FAQ before posting this
> question. I have a specific requirment - creating,modifying and deleting
> data structures inside the kernel values of which will be passed by an
> user application. I know we could do this by writing a system call or by
> ioctl command to a character device. My question is can we do this by
> writing to /proc file system ? Can we actually create, modify and delete
> data structures by accessing this file system ?
You could definitely use procfs, but it sounds like your example would
be complex. Lately mounting filesystems has become a cheap operation in
Linux. Mount/umount is also a convenient synchronization point. So,
maybe consider implementing your own tiny filesystems - a data
filesystem, where you mmap(2)/read(2)/write(2) data values, and a
control filesystem, where you control the system and manipulate data
values.
That way, you can use standard Unix syscalls, standard Unix tools and
standard Unix permissions to accomplish your domain-specific task.
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
prev parent reply other threads:[~2001-04-09 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 19:41 Question on accessing /proc Srinivasan Venkatraman
2001-04-09 19:51 ` Jeff Garzik [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=3AD212D4.55E5E8DB@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@dcs.uky.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