All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Writing forward compatible applications using /proc
Date: Sun, 12 Aug 2001 22:46:02 +0200	[thread overview]
Message-ID: <20010812224602.B6589@vestdata.no> (raw)
In-Reply-To: <20010812222139.A14464@dardhal.mired.net>; from jdomingo@internautas.org on Sun, Aug 12, 2001 at 10:21:39PM +0000

On Sun, Aug 12, 2001 at 10:21:39PM +0000, Jos� Luis Domingo L�pez wrote:
> > On 12 Aug 2001 13:54:02 +0000, Jos� Luis Domingo L�pez wrote:
> > > 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.
> > > 
> >
> Check this linux kernel mailing list for the (still scarce) details about
> "removing" kernel tunables from /proc:
> http://uwsg.iu.edu/hypermail/linux/kernel/0105.3/1439.html
> 
> To be precise, dicussion about modifying existing /proc starts here:
> http://uwsg.iu.edu/hypermail/linux/kernel/0105.3/1469.html
> 
> There were not much discussion about the subject, but it seems that in
> 2.5.x /proc will just hold information about running processes. The rest
> is still to be defined :)

If I'm not mistaken, the idea is to move everything not process related
from procfs to a dedicated sysfs. 

I don't think it has ever been proposed to not have a fs interface to
the data, but some changes have been proposed:
* Some standard way of parsing the files (e.g. xml)
* One file pr value, rather than today's system where you have to parse 
  the files
* Changing the directory layout.


-- 
Ragnar Kjorstad
Big Storage

  reply	other threads:[~2001-08-12 20:46 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
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 [this message]
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=20010812224602.B6589@vestdata.no \
    --to=lvm@ragnark.vestdata.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.