public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: Jan Engelhardt <jengelh-bdq14YP6qtRlEiWPh9xO2Q@public.gmane.org>
Cc: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linuxram-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
	viro-rfM+Q5joDG/XmaaqVzeoHQ@public.gmane.org,
	hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
	a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org
Subject: Re: [patch] VFS: extend /proc/mounts
Date: Wed, 16 Jan 2008 16:09:30 -0800	[thread overview]
Message-ID: <20080116160930.28168da3.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0801170057520.31385-vVwEwcwQeYFPkBl3ERsXe1l1cybopEuJUBSOeVevoDU@public.gmane.org>

On Thu, 17 Jan 2008 00:58:06 +0100 (CET) Jan Engelhardt <jengelh-bdq14YP6qtRlEiWPh9xO2Q@public.gmane.org> wrote:

> 
> On Jan 17 2008 00:43, Karel Zak wrote:
> >> 
> >> Seems like a plain bad idea to me.  There will be any number of home-made
> >> /proc/mounts parsers and we don't know what they do.
> >
> > So, let's use /proc/mounts_v2  ;-)
> 
> Was not it like "don't use /proc for new things"?

Well yeah.  If we're going to do a brand new mechanism to expose
per-mount data then we should hunker down and get it right.

  parent reply	other threads:[~2008-01-17  0:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 22:12 [patch] VFS: extend /proc/mounts Miklos Szeredi
2008-01-16 22:30 ` Andrew Morton
     [not found]   ` <20080116143051.ec488f3d.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-01-16 23:15     ` Miklos Szeredi
2008-01-16 23:43     ` Karel Zak
2008-01-16 23:58       ` Jan Engelhardt
     [not found]         ` <Pine.LNX.4.64.0801170057520.31385-vVwEwcwQeYFPkBl3ERsXe1l1cybopEuJUBSOeVevoDU@public.gmane.org>
2008-01-17  0:09           ` Andrew Morton [this message]
2008-01-17  3:35             ` Al Viro
2008-01-17  0:33         ` Neil Brown
2008-01-17  1:17           ` Jan Engelhardt
     [not found]           ` <18318.41541.386224.301640-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-01-17  8:55             ` Miklos Szeredi
     [not found]               ` <E1JFQWv-00061b-QA-8f8m9JG5TPIdUIPVzhDTVZP2KDSNp7ea@public.gmane.org>
2008-01-17 15:36                 ` Chuck Lever
2008-01-17  2:45   ` H. Peter Anvin
     [not found] ` <E1JFGUp-00054z-KQ-8f8m9JG5TPIdUIPVzhDTVZP2KDSNp7ea@public.gmane.org>
2008-01-17  3:33   ` Al Viro
2008-01-17  8:36     ` Miklos Szeredi
2008-01-17 10:34       ` Karel Zak

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=20080116160930.28168da3.akpm@linux-foundation.org \
    --to=akpm-de/tnxtf+jlsfhdxvbkv3wd2fqjk+8+b@public.gmane.org \
    --cc=a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=jengelh-bdq14YP6qtRlEiWPh9xO2Q@public.gmane.org \
    --cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linuxram-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org \
    --cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=viro-rfM+Q5joDG/XmaaqVzeoHQ@public.gmane.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