From: Andreas Haumer <andreas@xss.co.at>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rootfs exposure in /proc/mounts
Date: Sun, 27 Oct 2002 11:21:15 +0100 [thread overview]
Message-ID: <3DBBBE1B.5050809@xss.co.at> (raw)
In-Reply-To: 3DBAEC79.5050605@pobox.com
Jeff Garzik wrote:
[...]
>
> Bug 1 - don't softlink directly to /proc/mounts :) embedded guys
> typically do this, and you see why it bites you in the ass :)
>
Jeff, this remembers me on some discussion on LKML we had almost
exactly 2 years ago (look for the thread starting with Message-ID
Pine.LNX.4.02.10010251043060.5657-100000@rimbaud.xss.co.at)
Do you remember?
My opinion on this issue is still the same:
- Not only "embedded guys" symlink /etc/mtab to /proc/mounts!
We do this for years now on our diskless workstations, because
here our root-fs (and therefore /etc) is mounted readonly and
so there is no way to update a _regular_ "/etc/mtab" file on
a running system.
- /etc should contain only static configuration information.
The table of mounted filesystems is not this kind of data.
It's state information and should live somewhere else.
- the table of mounted filesystems is information which
the kernel must have, anyway. Why maintain a separate
file in userspace?
Comments?
- Andreas
--
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
next prev parent reply other threads:[~2002-10-27 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 18:53 rootfs exposure in /proc/mounts Andreas Steinmetz
2002-10-26 18:59 ` Alexander Viro
2002-10-26 19:12 ` Andreas Steinmetz
2002-10-26 19:26 ` Jeff Garzik
2002-10-27 0:22 ` Andreas Steinmetz
2002-10-27 10:21 ` Andreas Haumer [this message]
2002-10-27 11:18 ` Willy Tarreau
2002-10-27 23:27 ` Michal Jaegermann
2002-10-28 9:05 ` Kasper Dupont
2002-10-27 15:02 ` Jeff Garzik
2002-10-27 15:09 ` Christoph Hellwig
2002-10-28 0:03 ` Kenneth Johansson
2002-10-28 0:18 ` Christoph Hellwig
2002-10-28 1:17 ` Rob Landley
2002-10-28 15:01 ` Christoph Hellwig
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=3DBBBE1B.5050809@xss.co.at \
--to=andreas@xss.co.at \
--cc=jgarzik@pobox.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 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.