problem with /mem [Re: ifupdown writes to /etc... a bug?]

[Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de>]

Hi,

after patching mount and sysvinit to work with /mem and
/etc/mtab -> /mem/state/mtab I stumbled across a big problem:

==================== /etc/init.d/umountfs ====================
...
umount -ttmpfs $FORCE -a -r
...
# We leave /proc mounted.
echo -n "Unmounting local filesystems... "
umount -tnoproc $FORCE -a -r
echo "done."

mount -n -o remount,ro /
==============================================================

After the first umount there is no more tmpfs. That usually just /tmp
which doesn't hurt. But why is that done anyway?

With /mem being a tmpfs /mem will be gone and a
/etc/mtab -> /mem/state/mtab will be broken. If proc is mounted (as it
should) /proc/mounts will then be used (i think).

Will that allways work? Should it be changed?

For example loopback devices will be umounted but not freed. Will that
sync the data to the loopback files or can data be lost there?

MfG
        Goswin

PS: patched mount and sysvinit debs are at
deb ftp://mrvn.homeip.net/ sid main
deb-src ftp://mrvn.homeip.net/ sid main