mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Whither the "system without /proc" crowd?
Date: Fri, 8 Nov 2002 18:26:16 +0000	[thread overview]
Message-ID: <200211081826.16168.landley@trommello.org> (raw)
In-Reply-To: <20021108135849.GZ32005@suse.de>

On Friday 08 November 2002 13:58, Jens Axboe wrote:

> Here's a patch that includes that feature, puts the tunables in sysfs
> (so you obviously need that mounted). In
>
> /sys/block/<disk>/iosched

Stupid question time:

A great deal of text has been expended over the years by people desperately 
trying to make sure you didn't need /proc mounted to have a usable system, 
for some definition of usable.  Now with rootfs, initramfs, sysfs, and the 
libfs inspired "make a filesystem rather than an ioctl" policy, the main 
argument against requiring the use of /proc is that it has a lot more gunk in 
it (left over from the days when it was the only ramfs type system to export 
values in) than anyone is comfortable with.  (The argument against /dev/pty 
largely seems to be inertia, now that the "number of ptys" issue as a config 
tunable seems to have been cleared up).

There seems to be some sort of nebulous plan for eventually stripping down 
/proc, perhaps making a "crapfs" that's a union mount on top of /proc 
providing deprecated legacy support for a release or two.  But I haven't 
heard it explicitly stated.

So my questions are:

1) will some subset of /proc, /sys, /dev/pty, etc become required at some 
point in the future on everything but the most customized embedded systems?  
Or is keeping the system usable without them still a goal?

2) Is there a plan to rehabilitate /proc?

(I ask because I don't know.  Maybe I missed some important posts...)

Rob

-- 
http://penguicon.sf.net - Terry Pratchett, Eric Raymond, Pete Abrams, Illiad, 
CmdrTaco, liquid nitrogen ice cream, and caffienated jello.  Well why not?

      reply	other threads:[~2002-11-08 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 17:49 2.5.46: ide-cd cdrecord success report MdkDev
2002-11-07 18:03 ` Jens Axboe
2002-11-07 19:01   ` Robinson Maureira Castillo
2002-11-07 18:07 ` Adam Kropelin
     [not found]   ` <32894.62.65.205.175.1036692849.squirrel@webmail.starman.ee>
2002-11-08  1:53     ` Adam Kropelin
2002-11-08  2:10       ` Andrew Morton
2002-11-08  2:49         ` Adam Kropelin
2002-11-08  8:05           ` Jens Axboe
2002-11-08 10:14             ` Ingo Oeser
2002-11-08 11:43               ` Jens Axboe
2002-11-08 13:58                 ` Jens Axboe
2002-11-08 18:26                   ` 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=200211081826.16168.landley@trommello.org \
    --to=landley@trommello.org \
    --cc=axboe@suse.de \
    --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

all inboxes | Powered by JetHome®