From: DervishD <lkml@dervishd.net>
To: Olaf Hering <olh@suse.de>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: OOM & [OT] util-linux-2.12e
Date: Mon, 20 Sep 2004 12:59:50 +0200 [thread overview]
Message-ID: <20040920105950.GI5482@DervishD> (raw)
In-Reply-To: <20040920094602.GA24466@suse.de>
Hi Olaf :)
* Olaf Hering <olh@suse.de> dixit:
> > then /etc/mtab can die. Comments? Better solutions?
> Andries, /etc/mtab is obsolete since the day when /proc/self/mounts was
> introduced. So, kill it today from your mount binary! TODAY. ...
Bad idea... ;))) I upgraded my 'mount' yesterday. I was using a
mount from Debian, from 1998 more or less, that worked flawlessly
except for the '--bind' feature and things like those. I used
/etc/mtab as a symlink to /proc/mounts, and all worked OK except for
the double root entry and the need to manually call losetup to delete
unused /dev/loop entries.
But after the upgrade I no longer could umount a filesystem that
I mounted as 'user', because the device is a symlink and the 'user'
option is not stored in /proc/mounts. So my problems were:
> - the 'user' option for umount must be handled in some way
> - loop mounts do not map to the real filename, users cant open the
> device node to run losetup on it. I think it will also get relative
> path names.
> - fix all broken apps that still rely on mtab. like GNU df(1)
Exactly!!! I will add the double root filesystem entry (one from
the device, the other one being 'rootfs / rootfs rw 0 0'). Until all
these problems are solved, is not a good idea to remove /etc/mtab :(
I have another issue with a chroot environment I have, which has
its own copy of proc and devpts mounted. Those appear in /proc/mounts
twice, but not in /etc/mtab (they appear in the /etc/mtab copy of the
chroot env).
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2004-09-20 10:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 22:05 OOM & [OT] util-linux-2.12e Andries.Brouwer
2004-09-20 9:46 ` Olaf Hering
2004-09-20 10:12 ` Andreas Schwab
2004-09-20 10:54 ` DervishD
2004-09-20 11:43 ` Andreas Schwab
2004-09-20 11:51 ` Paulo Marques
2004-09-20 12:11 ` DervishD
2004-09-20 12:14 ` Andreas Schwab
2004-09-20 12:00 ` DervishD
2004-09-20 10:23 ` Roman Zippel
2004-09-20 10:56 ` Olaf Hering
2004-09-20 11:16 ` Roman Zippel
2004-09-20 11:26 ` Olaf Hering
2004-09-20 11:38 ` Roman Zippel
2004-09-20 11:50 ` Olaf Hering
2004-09-20 12:02 ` Roman Zippel
2004-09-20 12:07 ` Olaf Hering
2004-09-20 12:14 ` Roman Zippel
2004-09-20 12:19 ` Olaf Hering
2004-09-20 12:34 ` Roman Zippel
2004-09-20 12:38 ` Olaf Hering
2004-09-20 12:51 ` Andreas Schwab
2004-09-20 12:54 ` Olaf Hering
2004-09-20 13:19 ` CaT
2004-09-20 13:33 ` Andreas Schwab
2004-09-20 13:15 ` CaT
2004-09-20 10:59 ` DervishD [this message]
2004-09-20 13:24 ` Helge Hafting
2004-09-20 13:21 ` Olaf Hering
2004-09-20 13:32 ` Helge Hafting
2004-09-20 14:12 ` Herbert Poetzl
2004-09-21 7:20 ` Helge Hafting
2004-09-21 9:18 ` Herbert Poetzl
2004-09-20 15:24 ` Tonnerre
2004-09-20 11:11 ` David Gómez
2004-09-20 11:06 ` DervishD
2004-09-20 11:38 ` Xavier Bestel
2004-09-20 11:59 ` DervishD
2004-09-20 12:32 ` Xavier Bestel
2004-09-20 14:16 ` Herbert Poetzl
2004-09-21 16:45 ` Jari Ruusu
2004-09-21 21:26 ` Andries Brouwer
2004-09-22 17:05 ` Jari Ruusu
2004-09-22 18:39 ` Andries Brouwer
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=20040920105950.GI5482@DervishD \
--to=lkml@dervishd.net \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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.