From: Torrey Hoffman <torrey.hoffman@myrio.com>
To: "'Jeremy Jackson'" <jerj@coplanar.net>, root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: on /etc/mtab vs. /proc/mounts (Was RE: Linux should better cope w ith power failure)
Date: Mon, 19 Mar 2001 15:05:55 -0800 [thread overview]
Message-ID: <B65FF72654C9F944A02CF9CC22034CE22E1B42@mail0.myrio.com> (raw)
(Recipients trimmed, as this is a major change of topic...)
[big cut]
> Actually, I think /etc/mtab is not needed at all.
This is already mostly correct, AFAIK.
My embedded system uses "busybox" for mount and umount, /etc/mtab
does not exist, and the root file system is readonly.
But if I do "umount -a" it works. So the busybox umount is already
reading /proc/mounts.
The only oddity I see with using /proc/mounts is that it shows:
/dev/root / ext2 rw 0 0
instead of
/dev/hda1 / ext2 rw 0 0
but this doesn't seem to cause any problems... even though /dev/root
does not exist (!)
In fact, the "mount" man page on my Mandrake 7.2 system says:
"It is possible to replace /etc/mtab by a symbolic link to
/proc/mounts..." and then goes on to describe some of the issues and
problems with doing so - loopback, and paths with spaces seem to
be the significant ones.
Hopefully those problems can and will be solved soon, and then
we can get rid of /etc/mtab completely, and keep the root partition
read only almost all the time.
Torrey Hoffman
next reply other threads:[~2001-03-19 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 23:05 Torrey Hoffman [this message]
2001-03-19 23:43 ` on /etc/mtab vs. /proc/mounts Guest section DW
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=B65FF72654C9F944A02CF9CC22034CE22E1B42@mail0.myrio.com \
--to=torrey.hoffman@myrio.com \
--cc=jerj@coplanar.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®