From: bert hubert <ahu@ds9a.nl>
To: cranium2003 <cranium2003@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc query
Date: Sun, 12 Dec 2004 13:58:41 +0100 [thread overview]
Message-ID: <20041212125840.GA15826@outpost.ds9a.nl> (raw)
In-Reply-To: <20041211025014.34677.qmail@web41409.mail.yahoo.com>
On Fri, Dec 10, 2004 at 06:50:14PM -0800, cranium2003 wrote:
> Can a user program be able to overwrite /proc entry
> with some changes to that /proc file frequently?
> can same file be able to read by kernel in its actual
> kernel execution?
Userspace can only set settings in the kernel when the kernel allows this.
Procfs is not a storage filesystem, it stores settings and exposes
information.
The kernel does not 'read' files in /proc per se, it has direct access to
the relevant settings.
Procfs is like a window on the kernel, and in some cases you can hand the
kernel new settings.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-12-12 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 2:50 cranium2003
2004-12-12 12:58 ` bert hubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-14 11:01 linux lover
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=20041212125840.GA15826@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=cranium2003@yahoo.com \
--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
all inboxes | Powered by JetHome®