busybox's implementation of mount differs from the standalone version in not refusing to mount entries on top of each other. With tmpfs entries where it's actually possible to do this, it succeeds. That is, if you have a tmpfs entry in /etc/fstab and run 'mount -a' over and over you get stacking mounts -- but only with busybox's implementation. If you try the same trick with the -v option using standalone mount you get an error:
==> sudo mount -a -v mount: proc already mounted on /proc mount: UUID=79f04f7c-1d73-45a4-b996-5a1e88c2127e already mounted on /boot mount: tmpfs already mounted on /var/tmp nothing was mounted Is this a bug or intentional? Thanks, --Eric -- ****************************************************************************** * From the desktop of: Eric House, [EMAIL PROTECTED] * * Crosswords 4.1.4 for PalmOS now ARM-native: xwords.sourceforge.net * ****************************************************************************** _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
