From: Werner Almesberger <wa@almesberger.net>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel@vger.kernel.org, procps-list@redhat.com,
kernel@theoesters.com, rml@tech9.net, miquels@cistron-office.nl,
xose@wanadoo.es, tab@tuxfamily.org
Subject: Re: [announce] procps 2.0.13 with NPTL enhancements
Date: Sun, 1 Jun 2003 01:53:31 -0300 [thread overview]
Message-ID: <20030601015331.A8352@almesberger.net> (raw)
In-Reply-To: <20030530062635.GM5643@fs.tum.de>; from bunk@fs.tum.de on Fri, May 30, 2003 at 08:26:36AM +0200
Adrian Bunk wrote:
> Disabling the proc filesystem is simple by unchecking one item in the
> kernel config menu and different from taking out "a chunk of libc" it's
> more or less supported.
It's worse: if a system is brought up for reduced operation, e.g.
with init=/bin/sh for repair work, it is not uncommon for /proc to
be absent.
Since it is not immediately obvious for a user whether a given
program depends on /proc or not, just crashing in such a situation
is clearly a case poor user interface design.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-06-01 4:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1054270854.22088.617.camel@cube>
2003-05-30 6:26 ` [announce] procps 2.0.13 with NPTL enhancements Adrian Bunk
2003-06-01 4:53 ` Werner Almesberger [this message]
2003-05-30 16:56 ` Xose Vazquez Perez
[not found] ` <3ED788B5.2080203@wanadoo.es>
2003-05-31 1:25 ` Albert Cahalan
2003-05-31 2:36 Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 18:59 Xose Vazquez Perez
2003-05-30 8:12 Paolo Ciarrocchi
2003-05-30 8:20 ` cosmos
2003-05-30 5:30 Albert Cahalan
2003-05-29 17:25 Xose Vazquez Perez
2003-05-29 18:08 ` Adrian Bunk
2003-05-29 11:16 ` Robert Love
2003-05-29 20:01 ` Vincent Hanquez
2003-05-29 15:40 ` Robert Love
2003-05-28 15:09 Robert Love
2003-05-28 23:19 ` Phil Oester
2003-05-28 16:22 ` Robert Love
2003-05-28 23:59 ` Miquel van Smoorenburg
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=20030601015331.A8352@almesberger.net \
--to=wa@almesberger.net \
--cc=albert@users.sourceforge.net \
--cc=bunk@fs.tum.de \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
--cc=procps-list@redhat.com \
--cc=rml@tech9.net \
--cc=tab@tuxfamily.org \
--cc=xose@wanadoo.es \
/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