linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andrew Morton <akpm@digeo.com>,
	"Frederick, Fabian" <Fabian.Frederick@prov-liege.be>
Cc: linux-kernel@vger.kernel.org
Subject: Union mounts (was: Re: sysfs-diskstat)
Date: Wed, 4 Jun 2003 16:19:38 -0400	[thread overview]
Message-ID: <200306041619.38928.rob@landley.net> (raw)
In-Reply-To: <20030604021716.0b2a121a.akpm@digeo.com>

On Wednesday 04 June 2003 05:17, Andrew Morton wrote:
> "Frederick, Fabian" <Fabian.Frederick@prov-liege.be> wrote:
> > Hi !
> >
> > 	Someone could tell me if the proc/diskstat stuff will be kept in 2.6
> > and above or do we have to refer _only_
> >  to sysfs by now ?
>
> death, taxes and /proc/diskstats.  It ain't going away.

Out of morbid curiosity, what's the status of union mounts?  I've had this 
sneaking suspicion that /proc would eventually be broken up into two 
filesystems: 1) what /proc was originally meant for (a subdirectory for each 
pid), 2) all the extra crap that got shoehorned into it back when it was the 
only synthetic filesystem (and after everybody got into the habit of putting 
synthetic fs stuff into /proc).

Of course making this work with legacy tools would require union mounting both 
procfs and crapfs onto /proc.  Which gets us back to "how are union mounts 
doing"?

Rob

> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      reply	other threads:[~2003-06-04 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04  8:10 sysfs-diskstat Frederick, Fabian
2003-06-04  9:17 ` sysfs-diskstat Andrew Morton
2003-06-04 20:19   ` Rob Landley [this message]

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=200306041619.38928.rob@landley.net \
    --to=rob@landley.net \
    --cc=Fabian.Frederick@prov-liege.be \
    --cc=akpm@digeo.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;
as well as URLs for NNTP newsgroup(s).