From: "José Luis Domingo López" <jdomingo@internautas.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Writing forward compatible applications using /proc
Date: Sun, 12 Aug 2001 13:54:02 +0000 [thread overview]
Message-ID: <20010812135402.A452@dardhal.mired.net> (raw)
In-Reply-To: <20010811235718.A20414@linux.com>
On Saturday, 11 August 2001, at 23:57:18 -0400,
Jason Tackaberry wrote:
> [...]
> I am curious if it's a silly idea to write an application that relies on
> the data in /proc? Do the kernel developers attempt to keep the data
> and format provided in /proc as stable as possible? Or is it fair game
> for trivial changes that could break applications that parse it? Should
> I use ioctl instead?
>
As far as I know, there are plans to remove much of the thingss that
currently appear under /proc. It seems that only information about
processes currently running will remain under /proc.
Kernel parameters, system information, kernel variables and kernel
tunables will probably disappear and will be replaced by some sort of
user-space application that will allow query and modfication of kernel
values and tunables. Something similar to Solaris' ndd, AFAIK.
Greetings.
--
Jos� Luis Domingo L�pez
Linux Registered User #189436 Debian GNU/Linux Potato (P166 64 MB RAM)
jdomingo EN internautas PUNTO org => � Spam ? Atente a las consecuencias
jdomingo AT internautas DOT org => Spam at your own risk
next prev parent reply other threads:[~2001-08-12 13:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 3:57 [linux-lvm] Writing forward compatible applications using /proc Jason Tackaberry
2001-08-12 13:54 ` José Luis Domingo López [this message]
2001-08-12 15:38 ` Jason Tackaberry
2001-08-12 18:39 ` José Luis Domingo López
2001-08-12 16:39 ` Steven Lembark
2001-08-13 1:55 ` Paul Jakma
2001-08-12 17:10 ` Eric M. Hopper
2001-08-12 22:21 ` José Luis Domingo López
2001-08-12 20:46 ` Ragnar Kjørstad
2001-08-12 22:35 ` Wichert Akkerman
2001-08-12 20:21 ` toon
2001-08-12 19:07 ` Joe Thornber
2001-08-12 19:13 ` Steven Lembark
2001-08-12 19:26 ` Joe Thornber
2001-08-12 19:51 ` Jason Tackaberry
2001-08-12 20:16 ` Ragnar Kjørstad
2001-08-13 9:08 ` Joe Thornber
2001-08-13 11:27 ` Wichert Akkerman
2001-08-13 12:48 ` Terje Kvernes
2001-08-13 23:49 ` Ragnar Kjørstad
2001-08-14 13:36 ` Heinz J . Mauelshagen
2001-08-14 0:31 ` Nathan Scott
2001-08-14 13:33 ` Heinz J . Mauelshagen
2001-08-13 15:13 ` Alasdair G Kergon
2001-08-13 17:58 ` Jason Tackaberry
2001-08-13 19:44 ` Michael Tokarev
2001-08-13 19:49 ` Wichert Akkerman
2001-08-13 20:18 ` Goetz Bock
2001-08-13 20:47 ` Joe Thornber
2001-08-13 20:31 ` Joe Thornber
2001-08-14 3:04 ` Mark van Walraven
2001-08-14 8:14 ` Joe Thornber
2001-08-14 17:50 ` Ragnar Kjørstad
2001-08-15 8:58 ` Heinz J . Mauelshagen
2001-08-13 9:10 ` Terje Kvernes
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=20010812135402.A452@dardhal.mired.net \
--to=jdomingo@internautas.org \
--cc=linux-lvm@sistina.com \
/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