Do not overload mount-call - trying to reduce confusion

The behaviour of calling 'mount' differed depending on whether it called
the busybox-mount, the mount of util-linux, the mount defined in
/lib/functions.sh and /lib/functions/boot.sh

/etc/preinit even included /lib/functions.sh and /lib/functions/boot.sh,
both re-defining 'mount'.

SVN-Revision: 34792

package/base-files/files/lib/firstboot/20_no_fo_mount_jffs

@@ -5,8 +5,8 @@
 
 no_fo_mount_jffs() {
     # initialize jffs2
-    mount "$mtdpart" /overlay -t jffs2 || exit
-    
+    mount -o noatime "$mtdpart" /overlay -t jffs2 || exit
+
     # workaround to ensure that union can attach properly
     sync
     ls /overlay >/dev/null

package/base-files/files/lib/firstboot/30_is_rootfs_mounted

@@ -4,7 +4,7 @@
 # Copyright (C) 2010 Vertical Communications
 
 skip_if_rootfs_mounted() {
-    mount "$mtdpart" /rom/overlay -t jffs2 || exit
+    mount -o noatime -t jffs2 "$mtdpart" /rom/overlay || exit
 }
 
 boot_hook_add switch2jffs skip_if_rootfs_mounted