All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Sendetzky <norbert@linuxnetworks.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] per-driver filesystems made easy
Date: Sun, 12 May 2002 17:47:54 -0100	[thread overview]
Message-ID: <200205121747.54744.norbert@linuxnetworks.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0205121050390.25791-100000@weyl.math.psu.edu>

On Sunday 12 May 2002 14:01, Alexander Viro wrote:
> On Sun, 12 May 2002, Norbert Sendetzky wrote:
> > I am wondering if this information isn't something that should be
> > located in a subdirectory of /proc, shouldn't it? And perhaps it
>
> No, it shouldn't.  Basically, it's an example of doing things
> without touching dungpiles - devfs, procfs and ioctls.  Aside of
> the fact that procfs is extremely ugly, it's bloated, choke-full of
> races and has zero granularity - it's all or nothing.  It's also a
> shared namespace - and we all know how well does that idea work;
> just look at NetSol<spit>...

Was there already any discussion about breaking procfs into serveral 
independent pieces like the one you have done and rebuilding the 
procfs tree by mounting these pieces unter /proc? Perhaps this could 
solve most of problems of procfs has today and will provide all 
things you want (small independent subtrees, granularity, multiple 
namespaces).


Norbert


      reply	other threads:[~2002-05-12 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-11 20:53 [RFC] per-driver filesystems made easy Alexander Viro
2002-05-12 16:03 ` Norbert Sendetzky
2002-05-12 15:01   ` Alexander Viro
2002-05-12 18:47     ` Norbert Sendetzky [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=200205121747.54744.norbert@linuxnetworks.de \
    --to=norbert@linuxnetworks.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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.