public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Andreas Haumer <andreas@xss.co.at>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: rootfs exposure in /proc/mounts
Date: Sun, 27 Oct 2002 12:18:56 +0100	[thread overview]
Message-ID: <20021027111856.GA789@alpha.home.local> (raw)
In-Reply-To: <3DBBBE1B.5050809@xss.co.at>

Hi !

I remember this discussion too, and am also used to symlink mtab to
/proc/mounts. But I also remember some people stating that /proc/mounts doesn't
contain all information (some mount flags, nfs options ...) which may be needed
for a mount -o remount, while mtab contains them.

I too agree that it's non-sense to have both mtab and /proc/mounts. If mounts
isn't usable, why keep it ? At the moment, the only reason why I would abandon
this symlink would be that mounts be removed from /proc entirely ! And I also
agree that mtab shouldn't be under /etc (this is the only file that needs to
be written to). At least, it should be moved to /var/state or something like
that, provided it's available early in the boot stage, but this issue is not a
kernel one anyway.

But at this time, I still think that a symlink to /proc/mounts is the safest
solution in embedded or diskless situations, because even if we cannot update
it for the very first mounts, at least it will be correct when /proc is
mounted.

May be we should just accept this case as a common one, and update tools
(mount, umount, df, ?) to be able to use both mtab and /proc/mounts, and simply
ignore any rootfs entry.

Just my 0.02 euros.
Willy


  reply	other threads:[~2002-10-27 11:12 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
2002-10-27 11:18         ` Willy Tarreau [this message]
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=20021027111856.GA789@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox