From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Karel Zak <kzak@redhat.com>, Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
util-linux-ng@vger.kernel.org, linuxram@us.ibm.com,
viro@ftp.linux.org.uk, hch@infradead.org, a.p.zijlstra@chello.nl
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@fbirervta.pbzchgretzou.qr>
On Thu, 17 Jan 2008 00:58:06 +0100 (CET) Jan Engelhardt <jengelh@computergmbh.de> 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.
WARNING: multiple messages have this Message-ID (diff)
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.
next prev parent reply other threads:[~2008-01-17 0:11 UTC|newest]
Thread overview: 23+ 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:12 ` Miklos Szeredi
2008-01-16 22:30 ` Andrew Morton
2008-01-16 23:15 ` Miklos Szeredi
2008-01-16 23:15 ` Miklos Szeredi
2008-01-16 23:43 ` Karel Zak
2008-01-16 23:43 ` Karel Zak
2008-01-16 23:58 ` Jan Engelhardt
2008-01-17 0:09 ` Andrew Morton [this message]
2008-01-17 0:09 ` Andrew Morton
2008-01-17 3:35 ` Al Viro
2008-01-17 0:33 ` Neil Brown
2008-01-17 0:33 ` Neil Brown
2008-01-17 1:17 ` Jan Engelhardt
2008-01-17 8:55 ` Miklos Szeredi
2008-01-17 8:55 ` Miklos Szeredi
2008-01-17 15:36 ` Chuck Lever
2008-01-17 15:36 ` Chuck Lever
2008-01-17 2:45 ` H. Peter Anvin
2008-01-17 3:33 ` Al Viro
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@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hch@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=util-linux-ng@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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.